CWE-680: Integer Overflow to Buffer Overflow

Code Examples & CVEs

Demonstrative Examples

The following image processing code allocates a table for images.

This code intends to allocate a table of size num_imgs, however as num_imgs grows large, the calculation determining the size of the list will eventually overflow (CWE-190). This will result in a very small list to be allocated instead. If the subsequent code operates on the list as if it were num_imgs long, it may result in many types of out-of-bounds problems (CWE-119).

BadC

img_t table_ptr; /*struct containing img data, 10kB each*/int num_imgs;...num_imgs = get_num_imgs();table_ptr = (img_t*)malloc(sizeof(img_t)*num_imgs);...

Observed CVE Examples (2)

CVE-2021-43537

Chain: in a web browser, an unsigned 64-bit integer is forcibly cast to a 32-bit integer (CWE-681) and potentially leading to an integer overflow (CWE-190). If an integer overflow occurs, this can cause heap memory corruption (CWE-122)

View Details

CVE-2017-1000121

chain: unchecked message size metadata allows integer overflow (CWE-190) leading to buffer overflow (CWE-119).

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect Integer Overflow to Buffer Overflow with Automated Static Analysis

Documented detection approaches include Automated Static Analysis, and Automated Dynamic Analysis; recorded impacts include Modify Memory, DoS: Crash, Exit, or Restart, and Execute Unauthorized Code or Commands; the entry maps to CAPEC-10, CAPEC-100, CAPEC-14, and CAPEC-24. Use these source-defined anchors to turn CWE-680 into implementation, review, and verification checks for the affected component.

CWE-680: Integer Overflow to Buffer Overflow — MITRE CWE

Prevent CWE-680 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-680, Integer Overflow to Buffer Overflow, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Triage CWE-680 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-680, Integer Overflow to Buffer Overflow, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-680

Apply MITRE's full root-cause mapping guidance when using CWE-680, Integer Overflow to Buffer Overflow. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-680 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-680, Integer Overflow to Buffer Overflow. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-680: Integer Overflow to Buffer Overflow?+

CWE-680: Integer Overflow to Buffer Overflow is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The 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.

What are the security consequences of Integer Overflow to Buffer Overflow?+

If exploited, CWE-680 (Integer Overflow to Buffer Overflow) it can compromise Integrity, Availability and Confidentiality, leading to outcomes such as Modify Memory, DoS: Crash, Exit, or Restart and Execute Unauthorized Code or Commands.

Which programming languages are affected by Integer Overflow to Buffer Overflow?+

CWE-680 commonly affects C, C++ and Memory-Unsafe. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Integer Overflow to Buffer Overflow?+

MITRE documents real CVEs mapped to CWE-680, including CVE-2021-43537 and CVE-2017-1000121. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-680 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-680: Integer Overflow to Buffer Overflow

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods