293
Weakness Ordinalities
Resultant :
Applicable Platforms
Language : C (Prevalence = Undetermined)
Language : C++ (Prevalence = Undetermined)
Likelihood Of Exploit
High
Common Consequences
Scope Impact Likelihood
Integrity
Confidentiality
Availability
Access Control
Modify Memory
Execute Unauthorized Code or Commands
Gain Privileges or Assume Identity
DoS: Crash, Exit, or Restart
Bypass Protection Mechanism
Clearly, write-what-where conditions can be used to write
data to areas of memory outside the scope of a policy.
Also, they almost invariably can be used to execute
arbitrary code, which is usually outside the scope of
a program's implicit security policy. If the attacker can
overwrite a pointer's worth of memory (usually 32 or 64
bits), they can redirect a function pointer to their own
malicious code. Even when the attacker can only modify
a single byte arbitrary code execution can be possible.
Sometimes this is because the same problem can be
exploited repeatedly to the same effect. Other times it
is because the attacker can overwrite security-critical
application-specific data -- such as a flag indicating
whether the user is an administrator.
Integrity DoS: Crash, Exit, or Restart
CWE Version 4.14
CWE-123: Write-what-where Condition
CWE-123: Write-what-where Condition