CWE-191

Base Abstraction Level
Pillar — Highest-level weakness category
Class — Abstract, language-independent
Base — Specific enough to detect
Variant — Tied to specific technology
Compound — Requires multiple weaknesses Draft MITRE CWE Status
Stable — Fully reviewed and complete
Draft — Under development, may change
Incomplete — Partially defined by MITRE
Deprecated — No longer recommended
Obsolete — Replaced by another CWE
Integer Underflow (Wrap or Wraparound)

Description

The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result.

This can happen in signed and unsigned cases.

Top Monitored CVEs

CVE-2024-38063
CRITICAL
9.8 70.6%
2024-08-13
CVE-2024-38074
CRITICAL
9.8 2.2%
2024-07-09
CVE-2023-28250
CRITICAL
9.8 2.0%
2023-04-11
CVE-2023-32014
CRITICAL
9.8 1.9%
2023-06-13
CVE-2023-24887
HIGH
8.8 1.6%
2023-04-11
CVE-2023-21708
CRITICAL
9.8 1.5%
2023-03-14
CVE-2023-21556
HIGH
8.1 1.5%
2023-01-10
CVE-2023-21684
HIGH
8.8 1.3%
2023-02-14

Consequences

Availability — DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Instability

This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.

Integrity — Modify Memory

If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.

Confidentiality, Availability, Access Control — Execute Unauthorized Code or Commands, Bypass Protection Mechanism

This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.

Detection

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.)