- What is CWE-942?
- The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
- What CVEs are caused by CWE-942?
- 90 recorded CVEs are attributed to CWE-942, including CVE-2025-27909, CVE-2024-37131, CVE-2023-50940.
- How do you prevent CWE-942?
- Define a restrictive Content Security Policy [REF-1486] or cross-domain policy file.
- How is CWE-942 detected?
- 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.)
- What are the consequences of CWE-942?
- Exploiting CWE-942 can lead to: Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Read Application Data, Varies by Context.
- Is CWE-942 actively exploited?
- 90 recorded CVEs are caused by CWE-942; none are currently in CISA's KEV catalog of actively exploited flaws.