CWE-124: Buffer Underwrite ('Buffer Underflow')

What is CWE-124?

CWE-124 is Buffer Underwrite ('Buffer Underflow'). The flaw arises when the product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer. The database currently holds 20 vulnerabilities mapped to CWE-124 and none of them are in the CISA Known Exploited Vulnerabilities catalog.

OWASP Top 10 Rank-
Related CVES (365 days)20
AbstractionBase
Likelihood of exploitMedium

Vulnerabilities mapped to CWE-124

20 vulnerabilities300% increase year over year

No data

No vulnerability data in CISA KEV for CWE-124

Official definition

ByMitre CWE

The product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.

Characteristics

Alternate terms

  • buffer underrun — Some prominent vendors and researchers use the term "buffer underrun". "Buffer underflow" is more commonly used, although both terms are also sometimes used to describe a buffer under-read (CWE-127).

Modes of introduction

  • Implementation: This typically occurs when a pointer or its index is decremented to a position before the buffer, when pointer arithmetic results in a position before the beginning of the valid memory location, or when a negative index is used.

Common consequences

ImpactScopeExplanation
Modify Memory, DoS: Crash, Exit, or RestartIntegrity, AvailabilityOut of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash.
Execute Unauthorized Code or Commands, Modify Memory, Bypass Protection Mechanism, OtherIntegrity, Confidentiality, Availability, Access Control, OtherIf the corrupted memory can be effectively controlled, it may be possible to execute arbitrary code. If the corrupted memory is data rather than instructions, the system will continue to function with improper changes, possibly in violation of an implicit or explicit policy. The consequences would only be limited by how the affected data is used, such as an adjacent memory location that is used to specify whether the user has special privileges.
Bypass Protection Mechanism, OtherAccess Control, OtherWhen the consequence is arbitrary code execution, this can often be used to subvert any other security service.

Risk mitigations

  1. RequirementsChoose a language that is not susceptible to these issues.
  2. ImplementationAll calculated values that are used as index or for pointer arithmetic should be validated to ensure that they are within an expected range.

Detection methods

MethodApproachEffectiveness
Automated Static AnalysisAutomated 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.)High
Automated Dynamic AnalysisUse 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].Crafted inputs are necessary to reach the code containing the error, such as generated by fuzzers. Also, these tools may reduce performance, and they only report the error condition - not the original mistake that led to the error.Moderate

Representative vulnerabilities

Sources (2)

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.