Category:Write-what-where Condition

From VulneraPedia

Jump to: navigation, search

Contents

CWE Identificator

123


Description

Description_Summary

Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

Exposure Period

  • Implementation

Applicable_Platforms

  • Language_Name: C
  • Language_Name: C++


Likelihood of Exploit

High

Causal Nature

Explicit

Common Consequences

Scope Effect
Access_Control 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), he can redirect a function pointer to his 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.
Availability Many memory accesses can lead to program termination, such as when writing to addresses that are invalid for the current process.
Other When the consequence is arbitrary code execution, this can often be used to subvert any other security service.

Potential Mitigations

Pre-design: Use a language that provides appropriate memory abstractions.

Architecture and Design

Integrate technologies that try to prevent the consequences of this problem.

Implementation

Take note of mitigations provided for other flaws in this taxonomy that lead to write-what-where conditions.

Operational: Use OS-level preventative functionality integrated after the fact. Not a complete solution.

This category currently contains no pages or media.

Facts about Write-what-where ConditionRDF feed
CWE Identificator123  +
Causal NatureExplicit
Consequence ScopeAccess Control  +, Availability  +, and Other  +
DescriptionDescription_Summary

Any cond Description_Summary

Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

Exposure Period

  • Implementation

Applicable_Platforms

  • Language_Name: C
  • Language_Name: C++

nguage_Name: C

  • Language_Name: C++
Exposure PeriodImplementation
LanguageC  +, and C++  +
LikelihoodHigh  +
MitigationPre-design: Use a language that provides appropriate memory abstractions.

, Architecture and Design

Integrate technologies that try to prevent the consequences of this problem. , Implementation

Take note of mitigations provided for other flaws in this taxonomy that lead to write-what-where conditions. , and Operational: Use OS-level preventative functionality integrated after the fact. Not a complete solution.

ProviderMITRE  +
ScaleHigh  +
SecurityAttributeAccess Control  +, Availability  +, and Other  +
Personal tools