CWE-680: Integer Overflow to Buffer Overflow
low-riskThe product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.
Common Consequences
Detection Methods
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.)
Use tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518].
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2022-24834 | 7.0 | 42.1% | — |
| CVE-2025-32023 | 7.0 | 12.6% | — |
| CVE-2018-8786 | 9.8 | 9.6% | — |
| CVE-2018-8787 | 9.8 | 8.7% | — |
| CVE-2018-8795 | 9.8 | 6.7% | — |
| CVE-2018-8794 | 9.8 | 6.0% | — |
| CVE-2021-32625 | 7.5 | 2.7% | — |
| CVE-2021-21783 | 9.8 | 2.1% | — |
| CVE-2022-35289 | 9.8 | 1.6% | — |
| CVE-2021-40417 | 9.8 | 1.5% | — |