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

Description

Common consequences· 1

• 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 private information from the victim's machine to the attacker, manipulate or steal cookies that may include session information, create malicious requests to a web site on behalf of the victim, or execute malicious code on the end user systems. Other damaging attacks include the disclosure of end user files, installation of Trojan horse programs, redirecting the user to some other page or site, running ActiveX controls (under Microsoft Internet Explorer) from sites that a user perceives as trustworthy, and modifying presentation of content.

Potential mitigations· 3

• [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.

(incoming)18

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.