Modes Of Introduction
Architecture and Design : This weakness is introduced during the design of an application when the architect does not specify that a linked external document should not be able to alter the location of the calling page.
Implementation : This weakness is introduced during the coding of an application when the developer does not include the noopener and/or noreferrer value for the rel attribute.
Applicable Platforms
Language
Name: JavaScript (Often)
Technologies
Class: Web Based (Often)
Common Consequences
Scope |
Impact |
Likelihood |
Confidentiality | Alter Execution Logic
Note: The user may be redirected to an untrusted page that contains undesired content or malicious script code. | |
Observed Examples
References |
Description |
| Library software does not use rel: "noopener noreferrer" setting, allowing tabnabbing attacks to redirect to a malicious page |
Potential Mitigations
Phases : Architecture and Design
Specify in the design that any linked external document must not be granted access to the location object of the calling page.
Phases : Implementation
When creating a link to an external document using the tag with a defined target, for example "_blank" or a named frame, provide the rel attribute with a value "noopener noreferrer".
If opening the external document in a new window via javascript, then reset the opener by setting it equal to null.
Phases : Implementation
Do not use "_blank" targets. However, this can affect the usability of the application.
Detection Methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness : High
Vulnerability Mapping Notes
Justification : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comment : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
References
REF-39
Target="_blank" - the most underestimated vulnerability ever
Alex Yumashev.
https://medium.com/@jitbit/target-blank-the-most-underestimated-vulnerability-ever-96e328301f4c REF-40
The target="_blank" vulnerability by example
Ben Halpern.
https://dev.to/ben/the-targetblank-vulnerability-by-example REF-958
About rel=noopener
Mathias Bynens.
https://mathiasbynens.github.io/rel-noopener/
Submission
Name |
Organization |
Date |
Date release |
Version |
David Deatherage |
Silicon Valley Bank |
2017-09-26 +00:00 |
2017-11-08 +00:00 |
2.12 |
Modifications
Name |
Organization |
Date |
Comment |
CWE Content Team |
MITRE |
2018-03-27 +00:00 |
updated Alternate_Terms, Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, References |
CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Applicable_Platforms, Relationships |
CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Potential_Mitigations |
CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Detection_Factors, Relationships |
CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
CWE Content Team |
MITRE |
2023-10-26 +00:00 |
updated Observed_Examples |