Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-416 (释放后使用) — Vulnerability Class 4332

4332 vulnerabilities classified as CWE-416 (释放后使用). AI Chinese analysis included.

CWE-416, Use After Free, is a critical memory safety weakness occurring when a program continues to reference a memory location after it has been deallocated. Attackers typically exploit this vulnerability by freeing an object and then rapidly reallocating that same memory block with attacker-controlled data. Because the original pointer still points to the now-invalid address, the application may inadvertently execute malicious code or corrupt memory structures, often leading to arbitrary code execution or denial of service. To prevent this, developers must rigorously manage memory lifecycles by nullifying pointers immediately after freeing them, ensuring no dangling references remain. Utilizing modern programming languages with automatic garbage collection or employing static analysis tools to detect invalid memory accesses further mitigates the risk, ensuring that freed memory is never accessed again during the program’s execution.

MITRE CWE Description
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Common Consequences (4)
Integrity Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity, Confidentiality, Availability Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap …
Mitigations (2)
Architecture and Design Choose a language that provides automatic memory management.
Implementation When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Effectiveness: Defense in Depth
Examples (2)
The following example demonstrates the weakness.
#include <stdio.h> #include <unistd.h> #define BUFSIZER1 512 #define BUFSIZER2 ((BUFSIZER1/2) - 8) int main(int argc, char **argv) { char *buf1R1; char *buf2R1; char *buf2R2; char *buf3R2; buf1R1 = (char *) malloc(BUFSIZER1); buf2R1 = (char *) malloc(BUFSIZER1); free(buf2R1); buf2R2 = (char *) malloc(BUFSIZER2); buf3R2 = (char *) malloc(BUFSIZER2); strncpy(buf2R1, argv[1], BUFSIZER1-1); free(buf1R1); free(buf2R2); free(buf3R2); }
Bad · C
The following code illustrates a use after free error:
char* ptr = (char*)malloc (SIZE); if (err) { abrt = 1; free(ptr); } ... if (abrt) { logError("operation aborted before commit", ptr); }
Bad · C
CVE ID Title CVSS Severity Published
CVE-2020-14381 linux kernel 资源管理错误漏洞 — kernel 7.8 - 2020-12-03
CVE-2020-25656 Linux kernel资源管理错误漏洞 — kernel 4.7 - 2020-12-02
CVE-2019-2393 Crash while joining collections with $lookup — MongoDB Server 6.5 Medium 2020-11-23
CVE-2020-25725 Xpdf 资源管理错误漏洞 — xpdf 5.0 Medium 2020-11-21
CVE-2020-24438 Acrobat Reader DC Use-After-Free Vulnerability Could Lead to Information Disclosure — Acrobat Reader 3.3 Low 2020-11-05
CVE-2020-24430 Acrobat Pro DC Use-After-Free vulnerability Could Lead to Arbitrary Code Execution — Acrobat Reader 7.8 High 2020-11-05
CVE-2020-24437 Acrobat Reader DC Use-After-Free Vulnerability Could Lead to Arbitrary Code Execution — Acrobat Reader 7.8 High 2020-11-05
CVE-2020-1909 Facebook WhatsApp for iOS logging library 资源管理错误漏洞 — WhatsApp Business for iOS 9.8 - 2020-11-03
CVE-2020-17417 Foxit Reader 资源管理错误漏洞 — Reader 7.8 - 2020-10-13
CVE-2020-17410 Foxit PhantomPDF 资源管理错误漏洞 — PhantomPDF 7.8 - 2020-10-13
CVE-2020-6115 Nitro Software Nitro Pro 资源管理错误漏洞 — Nitro Pro 7.8 - 2020-09-17
CVE-2020-7068 Use of freed hash key in the phar_parse_zipfile function — PHP 4.8 Medium 2020-09-09
CVE-2020-14373 Artifex Software ghostscript 资源管理错误漏洞 — ghostscript 5.0 - 2020-09-03
CVE-2020-10720 Linux kernel 资源管理错误漏洞 — Kernel 5.5 - 2020-09-03
CVE-2020-5378 Dell G7 17 7790 BIOS 资源管理错误漏洞 — CPG BIOS 6.8 Medium 2020-09-02
CVE-2020-5376 Dell Inspiron 7347 BIOS 资源管理错误漏洞 — CPG BIOS 6.8 Medium 2020-09-02
CVE-2020-15637 Foxit Reader和PhantomPDF 资源管理错误漏洞 — PhantomPDF 3.3 - 2020-08-19
CVE-2020-7827 DaviewIndy Use-After-Free Vulnerability — DavieIndy 7.8 High 2020-07-30
CVE-2020-4060 Use After Free in in cups_update_info in LoRa Basics Station — LoRa Basics Station 4.1 Medium 2020-06-22
CVE-2020-4031 Use-After-Free in gdi_SelectObject in FreeRDP — FreeRDP 3.5 Low 2020-06-22
CVE-2019-19162 Tobesoft Xplatform 资源管理错误漏洞 — XPLATFORM 7.8 High 2020-05-11
CVE-2020-10690 Linux kernel 资源管理错误漏洞 — kernel 6.5 Medium 2020-05-08
CVE-2020-10700 Samba 资源管理错误漏洞 — samba 5.3 Medium 2020-05-04
CVE-2020-1752 GNU C Library 资源管理错误漏洞 — glibc 7.0 High 2020-04-30
CVE-2020-10906 Foxit Reader和PhantomPDF 资源管理错误漏洞 — Reader 7.8 - 2020-04-22
CVE-2020-10907 Foxit Reader和PhantomPDF 资源管理错误漏洞 — Reader 7.8 - 2020-04-22
CVE-2020-10900 Foxit Reader和PhantomPDF 资源管理错误漏洞 — Reader 7.8 - 2020-04-22
CVE-2020-10899 Foxit Reader和PhantomPDF 资源管理错误漏洞 — Reader 7.8 - 2020-04-22
CVE-2020-1983 libslirp: use after free vulnerability cause a denial of service. — libslirp 7.5 High 2020-04-22
CVE-2020-5348 Dell Latitude 7202 Rugged Tablet BIOS 资源管理错误漏洞 — CPG BIOS 6.8 Medium 2020-04-03

Vulnerabilities classified as CWE-416 (释放后使用) represent 4332 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.