1827
ChildOf 863 Incorrect Authorization 1787
CanPrecede 668 Exposure of Resource to Wrong Sphere 1469
Relevant to the view "Architectural Concepts" (CWE-1008)
Nature Type ID Name Page
MemberOf 1011 Authorize Actors 2425
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Technology : Web Based (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Confidentiality
Integrity
Availability
Access Control
Execute Unauthorized Code or Commands
Bypass Protection Mechanism
Read Application Data
Varies by Context
An attacker may be able to bypass the web browser's
same-origin policy. An attacker can exploit the weakness
to manipulate or steal cookies, create requests that
can be mistaken for those of a valid user, compromise
confidential information, or execute malicious code on
the end user systems for a variety of nefarious purposes.
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.
Detection Methods
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.)
Effectiveness = High
Potential Mitigations
CWE Version 4.14
CWE-942: Permissive Cross-domain Policy with Untrusted Domains
CWE-942: Permissive Cross-domain Policy with Untrusted Domains