CWE-942Permissive Cross-domain Security Policy with Untrusted Domains

Description

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.

[object Object]

Common consequences

• Confidentiality,Integrity,Availability,Access Control→Execute Unauthorized Code or Commands,Bypass Protection Mechanism,Read Application Data,Varies by Context
  With an overly permissive policy file, an attacker may be able to bypass the web browser's same-origin policy and conduct many of the same attacks seen in Cross-Site Scripting (CWE-79). An attacker can exploit the weakness to transfer priva

Potential mitigations

• Architecture and Design,Operation
  Define a restrictive Content Security Policy [REF-1486] or cross-domain policy file.
• Architecture and Design,Operation
  Avoid using wildcards in the CSP / cross-domain policy file. Any domain matching the wildcard expression will be implicitly trusted, and can perform two-way interaction with the target server.
• Architecture and Design,Operation
  For Flash, modify crossdomain.xml to use meta-policy options such as 'master-only' or 'none' to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.

Related CWEs

Recent CVEs classified under this CWE