CWE-415Double Free

Description

The product calls free() twice on the same memory address.

Common consequences

• Integrity,Confidentiality,Availability→Modify Memory,Execute Unauthorized Code or Commands
  [object Object]

Potential mitigations

• Architecture and Design
  Choose a language that provides automatic memory management.
• Implementation
  Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
• Implementation
  Use a static analysis tool to find double free instances.

Related CWEs

Recent CVEs classified under this CWE