CWE-415: Double Free
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product calls free() twice on the same memory address.
常见后果
影响范围: Integrity Confidentiality Availability
技术影响: Modify Memory Execute Unauthorized Code or Commands
潜在缓解措施
阶段: 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.
检测方法
方法: Fuzzing
Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
有效性: High
方法: Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
有效性: High
观察示例
参考: CVE-2006-5051
Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).
参考: CVE-2004-0642
Double free resultant from certain error conditions.
参考: CVE-2004-0772
Double free resultant from certain error conditions.
参考: CVE-2005-1689
Double free resultant from certain error conditions.
参考: CVE-2003-0545
Double free from invalid ASN.1 encoding.
参考: CVE-2003-1048
Double free from malformed GIF.
参考: CVE-2005-0891
Double free from malformed GIF.
参考: CVE-2002-0059
Double free from malformed compressed data.
引入模式
| 阶段 | 说明 |
|---|---|
| Implementation | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| PLOVER | - | DFREE - Double-Free Vulnerability | - |
| 7 Pernicious Kingdoms | - | Double Free | - |
| CLASP | - | Doubly freeing memory | - |
| CERT C Secure Coding | MEM00-C | Allocate and free memory in the same module, at the same level of abstraction | - |
| CERT C Secure Coding | MEM01-C | Store a new value in pointers immediately after free() | - |
| CERT C Secure Coding | MEM30-C | Do not access freed memory | CWE More Specific |
| CERT C Secure Coding | MEM31-C | Free dynamically allocated memory exactly once | - |
| Software Fault Patterns | SFP12 | Faulty Memory Release | - |