CWE-786: Access of Memory Location Before Start of Buffer

BaseIncomplete

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

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
DISCOURAGED

Applicable To

Languages
CC++Memory-Unsafe
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect Access of Memory Location Before Start of Buffer with Fuzzing

Documented detection approaches include Fuzzing, and Automated Dynamic Analysis; recorded impacts include Read Memory, Modify Memory, DoS: Crash, Exit, or Restart, and Execute Unauthorized Code or Commands; observed examples include CVE-2002-2227, CVE-2007-4580, and CVE-2007-1584. Use these source-defined anchors to turn CWE-786 into implementation, review, and verification checks for the affected component.

CWE-786: Access of Memory Location Before Start of BufferMITRE CWE

Prevent CWE-786 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-786, Access of Memory Location Before Start of Buffer, 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 FrameworkNational Institute of Standards and Technology

Triage CWE-786 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-786, Access of Memory Location Before Start of Buffer, 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 CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-786

Apply MITRE's full root-cause mapping guidance when using CWE-786, Access of Memory Location Before Start of Buffer. 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 GuidanceMITRE CWE

Validate CWE-786 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-786, Access of Memory Location Before Start of Buffer. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-786: Access of Memory Location Before Start of Buffer?+

CWE-786: Access of Memory Location Before Start of Buffer is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product reads or writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer. 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.

What are the security consequences of Access of Memory Location Before Start of Buffer?+

If exploited, CWE-786 (Access of Memory Location Before Start of Buffer) it can compromise Confidentiality, Integrity and Availability, leading to outcomes such as Read Memory, Modify Memory, DoS: Crash, Exit, or Restart and Execute Unauthorized Code or Commands.

Which programming languages are affected by Access of Memory Location Before Start of Buffer?+

CWE-786 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 Access of Memory Location Before Start of Buffer?+

MITRE documents real CVEs mapped to CWE-786, including CVE-2002-2227, CVE-2007-4580, CVE-2007-1584, CVE-2007-0886 and CVE-2006-6171. 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-786 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.

Learn More

Advertisement