CAPECattack pattern
CAPEC-92 Forced Integer Overflow
High
Official page ↗
- Abstraction
- Detailed
- Status
- Draft
- Likelihood of attack
- High
- Typical severity
- High
- CAPEC version
- 3.9
Description
This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.
Execution flow
1. [Explore] The first step is exploratory meaning the attacker looks for an integer variable that they can control.
2. [Experiment] The attacker finds an integer variable that they can write into or manipulate and try to get the value of the integer out of the possible range.
3. [Exploit] The integer variable is forced to have a value out of range which set its final value to an unexpected value.
4. [Exploit] The target host acts on the data and unexpected behavior may happen.
Prerequisites
• The attacker can manipulate the value of an integer variable utilized by the target host.
• The target host does not do proper range checking on the variable before utilizing it.
• When the integer variable is incremented or decremented to an out of range value, it gets a very different value (e.g. very small or negative number)
Skills required
• [Low] An attacker can simply overflow an integer by inserting an out of range value.
• [High] Exploiting a buffer overflow by injecting malicious code into the stack of a software system or even the heap can require a higher skill level.
Consequences
• Integrity: Modify Data
• Confidentiality, Access Control, Authorization: Gain Privileges
• Confidentiality, Integrity, Availability: Execute Unauthorized Commands
• Confidentiality: Read Data
• Availability: Unreliable Execution
Mitigations
• Use a language or compiler that performs automatic bounds checking.
• Carefully review the service's implementation before making it available to user. For instance you can use manual or automated code review to uncover vulnerabilities such as integer overflow.
• Use an abstraction library to abstract away risky APIs. Not a complete solution.
• Always do bound checking before consuming user input data.
Related
Child of · CAPEC (1)
- CAPEC-128 Integer Attacks attack pattern
Weakness · CWE (7)
- CWE-120 Buffer Copy without Checking Size of Input weakness
- CWE-122 Heap-based Buffer Overflow weakness
- CWE-128 Wrap-around Error weakness
- CWE-190 Integer Overflow or Wraparound weakness
- CWE-196 Unsigned to Signed Conversion Error weakness
- CWE-680 Integer Overflow to Buffer Overflow weakness
- CWE-697 Incorrect Comparison weakness
Referenced by CWE · attack pattern (7)
- CWE-120 Buffer Copy without Checking Size of Input weakness
- CWE-122 Heap-based Buffer Overflow weakness
- CWE-128 Wrap-around Error weakness
- CWE-190 Integer Overflow or Wraparound weakness
- CWE-196 Unsigned to Signed Conversion Error weakness
- CWE-680 Integer Overflow to Buffer Overflow weakness
- CWE-697 Incorrect Comparison weakness