CAPEC Definitions / CAPEC-8
CAPEC-8: Buffer Overflow in an API Call
This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An adversary who has knowledge of known vulnerable libraries or shared code can easily target software that makes use of these libraries. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
Extended Description
No Extended Description.
Mitigations
Use a language or compiler that performs automatic bounds checking.
Use secure functions not vulnerable to buffer overflow.
If you have to use dangerous functions, make sure that you do boundary checking.
Compiler-based canary mechanisms such as StackGuard, ProPolice and the Microsoft Visual Studio /GS flag. Unless this provides automatic bounds checking, it is not a complete solution.
Use OS-level preventative functionality. Not a complete solution.
Relationships with other CAPECs
CAPEC-100: Overflow Buffers
Prerequisites
The target host exposes an API to the user.
One or more API functions exposed by the target host has a buffer overflow vulnerability.
Related Weaknesses
CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-118: Incorrect Access of Indexable Resource ('Range Error')
CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CWE-20: Improper Input Validation
CWE-680: Integer Overflow to Buffer Overflow
CWE-733: Compiler Optimization Removal or Modification of Security-critical Code
CWE-697: Incorrect Comparison
