Release of Invalid Pointer or Reference

Opis

The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.

This weakness can take several forms, such as:

- The memory was allocated, explicitly or implicitly, via one memory management method and deallocated using a different, non-compatible function (CWE-762).

- The function calls or memory management routines chosen are appropriate, however they are used incorrectly, such as in CWE-761.

Skutki

• Integrity, Availability, Confidentiality

  Modify Memory; DoS: Crash, Exit, or Restart; Execute Unauthorized Code or Commands

  This weakness may result in the corruption of memory, and perhaps instructions, possibly leading to a crash. If the corrupted memory can be effectively controlled, it may be possible to execute arbitrary code.

Zapobieganie

• Implementation

  Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().

• Implementation

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

• Architecture and Design · Libraries or Frameworks

  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.

• Architecture and Design

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

Przykłady podatności

• CVE-2019-11930 function "internally calls 'calloc' and returns a pointer at an index... inside the allocated buffer. This led to freeing invalid memory."

Słabość nadrzędna

• CWE-404 Improper Resource Shutdown or Release

Słabości podrzędne

• CWE-761 Free of Pointer not at Start of Buffer
• CWE-762 Mismatched Memory Management Routines

Kiedy powstaje

• Implementation

Dotyczy

Memory-Unsafe, C, C++

Uwagi

The view-1000 subtree that is associated with this weakness needs additional work. Several entries will likely be created in this branch. Currently the focus is on free() of memory, but delete and other related release routines may require the creation of intermediate entries that are not specific to a particular function. In addition, the role of other types of invalid pointers, such as an expired pointer, i.e. CWE-415 Double Free and release of uninitialized pointers, related to CWE-457.

Źródła

1. boost C++ Library Smart Pointers
2. Valgrind
3. AddressSanitizer