- What is CWE-128?
- Wrap around errors occur whenever a value is incremented past the maximum value for its type and therefore "wraps around" to a very small, negative, or undefined value.
- What CVEs are caused by CWE-128?
- 3 recorded CVEs are attributed to CWE-128, including CVE-2024-23981, CVE-2022-35258, CVE-2026-54905.
- How do you prevent CWE-128?
- Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
- How is CWE-128 detected?
- 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.)
- What are the consequences of CWE-128?
- Exploiting CWE-128 can lead to: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Instability, Modify Memory, Execute Unauthorized Code or Commands.
- Is CWE-128 actively exploited?
- 3 recorded CVEs are caused by CWE-128; none are currently in CISA's KEV catalog of actively exploited flaws.
