Nama: Use of Web Link to Untrusted Target with window.opener Access

The web application produces links to untrusted external sites outside of its sphere of control, but it does not properly prevent the external site from modifying security-critical properties of the window.opener object, such as the location property.

Informasi Umum

Detail Latar Belakang

Mode Pengenalan

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.

Platform yang Berlaku

Bahasa

Kelas: Not Language-Specific (Undetermined)
Nama: JavaScript (Often)

Teknologi

Kelas: Web Based (Often)
Nama: Web Server (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Confidentiality	Alter Execution Logic Catatan: If an attacker can run script on the target page, then they could read or modify certain properties of the window.opener object, including the location property - even if the original and target site are not the same origin. An attacker can modify the location property to automatically redirect the user to an untrusted page that contains undesired content or malicious script code, e.g. as part of a phishing attack. Since this redirect happens in the original window/tab - which is not necessarily visible, since the browser is focusing the display on the new target page - the user might not notice any suspicious redirection.

Contoh yang Diamati

Referensi	Deskripsi
CVE-2022-4927	Library software does not use rel: "noopener noreferrer" setting, allowing tabnabbing attacks to redirect to a malicious page

Mitigasi yang Memungkinkan

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
Phases : Implementation

Metode Deteksi

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.)
Efektivitas : High

Catatan Pemetaan Kerentanan

Justifikasi : 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.
Komentar : 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.

Referensi

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
David Deatherage	Silicon Valley Bank	2017-09-26 +00:00	2017-11-08 +00:00	2.12

Modifikasi

Nama	Organisasi	Tanggal	Komentar
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
CWE Content Team	MITRE	2025-12-11 +00:00	updated Applicable_Platforms, Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2026-10-28 +00:00	updated Background_Details, Common_Consequences, Description

Detail CWE-1022

CWE-1022