CWE-761: Free of Pointer not at Start of Buffer

VariantIncomplete

The product calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer.

View on MITRE
Back to CWE Lookup

Extended Description

This can cause the product to crash, or in some cases, modify critical program variables or execute code. This weakness often occurs when the memory is allocated explicitly on the heap with one of the malloc() family functions and free() is called, but pointer arithmetic has caused the pointer to be in the interior or end of the buffer.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
CMemory-Unsafe
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-761 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-761, Free of Pointer not at Start of Buffer, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Apply Libraries or Frameworks controls for Free of Pointer not at Start of Buffer

MITRE associates mitigation with Implementation, and Architecture and Design; the listed strategies include Libraries or Frameworks; documented detection approaches include Automated Dynamic Analysis. Use these source-defined anchors to turn CWE-761 into implementation, review, and verification checks for the affected component.

CWE-761: Free of Pointer not at Start of BufferMITRE CWE

Triage CWE-761 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-761, Free of Pointer not at 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-761

Apply MITRE's full root-cause mapping guidance when using CWE-761, Free of Pointer not at 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-761 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-761, Free of Pointer not at 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-761: Free of Pointer not at Start of Buffer?+

CWE-761: Free of Pointer not at Start of Buffer is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer. This can cause the product to crash, or in some cases, modify critical program variables or execute code. This weakness often occurs when the memory is allocated explicitly on the heap with one of the malloc() family functions and free() is called, but pointer arithmetic has caused the pointer to be in the interior or end of the buffer.

What are the security consequences of Free of Pointer not at Start of Buffer?+

If exploited, CWE-761 (Free of Pointer not at Start of Buffer) 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.

How do you prevent or mitigate Free of Pointer not at Start of Buffer?+

Recommended mitigations for CWE-761 include: When utilizing pointer arithmetic to traverse a buffer, use a separate variable to track progress through memory and preserve the originally allocated address for later freeing. When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory. Use a language that provides abstractions for memory allocation and deallocation.

Which programming languages are affected by Free of Pointer not at Start of Buffer?+

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

What are real-world examples of Free of Pointer not at Start of Buffer?+

MITRE documents real CVEs mapped to CWE-761, including CVE-2019-11930. 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-761 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