CWE-1022 Variante Incomplet Medium likelihood

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

This vulnerability occurs when a web application links to an external, untrusted site without protecting its own window from being manipulated by that site. Specifically, it fails to prevent the…

Définition

What is CWE-1022?

This vulnerability occurs when a web application links to an external, untrusted site without protecting its own window from being manipulated by that site. Specifically, it fails to prevent the external page from altering security-sensitive properties of the `window.opener` object, such as the page's location.
When a link with `target="_blank"` opens an external site in a new tab, the new page gains a reference back to the originating page via the `window.opener` object. If the external site is compromised or malicious, it can execute scripts that read or modify properties of the `window.opener` object. This cross-origin access allows an attacker to, for example, silently change the `location` property of your original page, redirecting it to a phishing site without the user's knowledge. Since the user's focus is on the newly opened tab, the original tab performing the redirect may not be visible. This makes the attack particularly stealthy, as users are unlikely to notice their original page has been hijacked until they return to it, potentially after entering sensitive information on a spoofed site.
Impact réel

Real-world CVEs caused by CWE-1022

  • CVE-2022-4927

    Library software does not use rel: "noopener noreferrer" setting, allowing tabnabbing attacks to redirect to a malicious page

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

  1. 1

    In this example, the application opens a link in a named window/tab without taking precautions to prevent the called page from tampering with the calling page's location in the browser.

  2. 2

    There are two ways that this weakness is commonly seen. The first is when the application generates an tag is with target="_blank" to point to a target site:

  3. 3

    If the attacker offers a useful page on this link (or compromises a trusted, popular site), then a user may click on this link. However, the attacker could use scripting code to modify the window.opener's location property to redirect the application to a malicious, attacker-controlled page - such as one that mimics the look and feel of the original application and convinces the user to re-enter authentication credentials, i.e. phishing:

  4. 4

    To mitigate this type of weakness, some browsers support the "rel" attribute with a value of "noopener", which sets the window.opener object equal to null. Another option is to use the "rel" attribute with a value of "noreferrer", which in essence does the same thing.

  5. 5

    A second way that this weakness is commonly seen is when opening a new site directly within JavaScript. In this case, a new site is opened using the window.open() function.

Exemple de code vulnérable

Vulnerable HTML

There are two ways that this weakness is commonly seen. The first is when the application generates an tag is with target="_blank" to point to a target site:

Vulnérable HTML 
<a href="http://attacker-site.example.com/useful-page.html" target="_blank">
Charge utile de l'attaquant

If the attacker offers a useful page on this link (or compromises a trusted, popular site), then a user may click on this link. However, the attacker could use scripting code to modify the window.opener's location property to redirect the application to a malicious, attacker-controlled page - such as one that mimics the look and feel of the original application and convinces the user to re-enter authentication credentials, i.e. phishing:

Charge utile de l'attaquant JavaScript 
window.opener.location = 'http://phishing.example.org/popular-bank-page';
Exemple de code sécurisé

Secure HTML

To mitigate this type of weakness, some browsers support the "rel" attribute with a value of "noopener", which sets the window.opener object equal to null. Another option is to use the "rel" attribute with a value of "noreferrer", which in essence does the same thing.

Sécurisé HTML 
<a href="http://attacker-site.example.com/useful-page.html" target="_blank" rel="noopener noreferrer">
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention

How to prevent CWE-1022

  • 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.
  • 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.
  • Implementation Do not use "_blank" targets. However, this can affect the usability of the application.
Signaux de détection

How to detect CWE-1022

Automated Static Analysis High

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.)

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-1022 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement
Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-1022 ?

This vulnerability occurs when a web application links to an external, untrusted site without protecting its own window from being manipulated by that site. Specifically, it fails to prevent the external page from altering security-sensitive properties of the `window.opener` object, such as the page's location.

Quelle est la gravité de CWE-1022 ?

MITRE évalue la probabilité d'exploitation comme Moyenne — l'exploitation est réaliste mais nécessite généralement des conditions spécifiques.

Quels langages ou plateformes sont affectés par CWE-1022 ?

MITRE lists the following affected platforms: JavaScript, Web Based.

Comment puis-je prévenir CWE-1022 ?

Specify in the design that any linked external document must not be granted access to the location object of the calling page. 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.

Comment Plexicus détecte et corrige CWE-1022 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-1022 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-1022 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/1022.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-1022

CWE-266 Parent

Incorrect Privilege Assignment

This vulnerability occurs when a system mistakenly grants a user, process, or entity a specific permission or privilege they should not…

CWE-520 Frère

.NET Misconfiguration: Use of Impersonation

This vulnerability occurs when a .NET application is configured to run with impersonation, potentially granting it excessive system-level…

CWE-556 Frère

ASP.NET Misconfiguration: Use of Identity Impersonation

This vulnerability occurs when an ASP.NET application is configured to run using impersonated credentials, which can grant the application…

CWE-9 Frère

J2EE Misconfiguration: Weak Access Permissions for EJB Methods

This vulnerability occurs when Enterprise JavaBean (EJB) methods are configured with overly permissive access rights, allowing attackers…

Ressources

Further reading

Prêt quand vous l'êtes

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo