CWE-761

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.

Common consequences1

• IntegrityAvailabilityConfidentialityModify MemoryDoS: Crash, Exit, or RestartExecute Unauthorized Code or Commands

Potential mitigations4

1. Implementation

   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.

2. Implementation

   When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.

3. Architecture and Design

   Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, glibc in Linux provides protection against free of invalid pointers.

4. Architecture and Design

   Use a language that provides abstractions for memory allocation and deallocation.

Relationships2

• ChildOfCWE-763
• ChildOfCWE-404