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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-122 (堆缓冲区溢出) — Vulnerability Class 2169

2169 vulnerabilities classified as CWE-122 (堆缓冲区溢出). AI Chinese analysis included.

CWE-122 represents a critical memory safety weakness where an application writes data beyond the allocated boundaries of a heap-allocated buffer, typically created via functions like malloc. This vulnerability arises when developers fail to validate input lengths or perform insufficient bounds checking before copying data into dynamically allocated memory regions. Attackers exploit this flaw by crafting malicious inputs that exceed buffer limits, allowing them to overwrite adjacent heap metadata or control structures. Such overwrites can corrupt the heap manager’s internal state, leading to application crashes, data leakage, or arbitrary code execution by hijacking control flow. To prevent heap-based buffer overflows, developers must rigorously validate all input sizes against buffer capacities, utilize safe string handling libraries that enforce length limits, and employ modern memory-safe programming languages that automatically manage memory boundaries, thereby eliminating manual pointer arithmetic errors.

MITRE CWE Description
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Common Consequences (3)
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)
Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
Integrity, Confidentiality, Availability, Access ControlExecute Unauthorized Code or Commands, Bypass Protection Mechanism, Modify Memory
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. Besides important user data, heap-based overflows can be used to overwrite function pointers that may be living in memory, pointing it to the attacker's code. Eve…
Integrity, Confidentiality, Availability, Access Control, OtherExecute Unauthorized Code or Commands, Bypass Protection Mechanism, Other
When the consequence is arbitrary code execution, this can often be used to subvert any other security service.
Mitigations (5)
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and DesignUse an abstraction library to abstract away risky APIs. Not a complete solution.
Operation, Build and CompilationUse automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses…
Effectiveness: Defense in Depth
Operation, Build and CompilationRun or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported…
Effectiveness: Defense in Depth
ImplementationImplement and perform bounds checking on input.
Examples (2)
While buffer overflow examples can be rather complex, it is possible to have very simple, yet still exploitable, heap-based buffer overflows:
#define BUFSIZE 256 int main(int argc, char **argv) { char *buf; buf = (char *)malloc(sizeof(char)*BUFSIZE); strcpy(buf, argv[1]); }
Bad · C
This example applies an encoding procedure to an input string and stores it into a buffer.
char * copy_input(char *user_supplied_string){ int i, dst_index; char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE); if ( MAX_SIZE <= strlen(user_supplied_string) ){ die("user string too long, die evil hacker!"); } dst_index = 0; for ( i = 0; i < strlen(user_supplied_string); i++ ){ if( '&' == user_supplied_string[i] ){ dst_buf[dst_index++] = '&'; dst_buf[dst_index++] = 'a'; dst_buf[dst_index++] = 'm'; dst_buf[dst_index++] = 'p'; dst_buf[dst_index++] = ';'; } else if ('<' == user_supplied_string[i] ){ /* encode to &lt; */ } else dst_buf[dst_index++] = user_supplied_string[i]; } return ds
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2026-15506 SecureAge CatchPulse Driver saappctl.sys heap-based overflow — CatchPulse 7.8 High2026-07-12
CVE-2026-56372 ImageMagick - Heap Buffer Overflow Read via Unrecognized Magnify Method — ImageMagick 3.3 Low2026-07-11
CVE-2026-57156 FreeRDP: Integer overflow leading to heap buffer overflow in Orders Delta Points parsing — FreeRDP--2026-07-10
CVE-2026-54000 osquery: Heap buffer overflow in `getProcessCurrentDirectory()` via `processes` table (Windows) — osquery--2026-07-10
CVE-2026-54001 osquery: Heap buffer overflow via `authenticode` table (Windows) — osquery--2026-07-10
CVE-2026-15182 GNU LibreDWG BMP Image dwg.c dwg_bmp heap-based overflow — LibreDWG 5.3 Medium2026-07-09
CVE-2026-58306 Samsung Open Source Escargot 缓冲区错误漏洞 — Escargot 6.1 Medium2026-07-09
CVE-2026-15174 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-07-08
CVE-2026-15173 Heap-based Buffer Overflow in Wireshark — Wireshark 4.7 Medium2026-07-08
CVE-2026-15169 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-07-08
CVE-2026-15170 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-07-08
CVE-2026-15165 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-07-08
CVE-2026-15164 Heap-based Buffer Overflow in ciscodump — ciscodump 5.5 Medium2026-07-08
CVE-2026-56003 libXfont2 computeProps Property Buffer Heap Buffer Overflow — libXfont2 8.5 High2026-07-08
CVE-2026-56002 libXfont2 PCF Font Parsing Heap Buffer Overflow — libXfont2 8.5 High2026-07-08
CVE-2026-56001 libXfont2 BitmapScaleBitmaps Integer Overflow Heap Buffer Overflow — libXfont2 8.5 High2026-07-08
CVE-2026-55999 xorg-server / xwayland glamor font atlas Heap Buffer Overflow — xorg-server 8.5 High2026-07-08
CVE-2026-58471 GNU Wget 1.25.0 Heap Buffer Overflow via convert_fname() in url.c — wget 5.9 Medium2026-07-07
CVE-2026-14940 389-ds-base: 389-ds-base: heap-buffer-overflow in dn normalization via quoted multivalued rdn — Red Hat Directory Server 11 5.3 Medium2026-07-07
CVE-2026-11610 389-ds-base: 389-ds-base: heap buffer overflow in sasl_io_recv() via padded sasl unbind — 389-ds-base 8.8 High2026-07-07
CVE-2025-15668 GPAC MP4Box box_code_base.c sgpd_del_entry heap-based overflow — GPAC 3.3 Low2026-07-06
CVE-2026-14759 radareorg radare2 RBinJava Line Number Table class.c r_bin_java_inner_classes_attr_calc_size heap-based overflow — radare2 3.3 Low2026-07-05
CVE-2026-14355 ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD — php 5.6 Medium2026-07-03
CVE-2026-14610 Open Asset Import Library Assimp CSM File CSMLoader.cpp InternReadFile heap-based overflow — Assimp 5.3 Medium2026-07-03
CVE-2026-56645 Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability — Microsoft Edge (Chromium-based) 8.8 High2026-07-03
CVE-2026-58379 Gimp: gimp: heap buffer overflow in read_channel_data() — Red Hat Enterprise Linux 9 7.3 High2026-07-03
CVE-2026-14427 Google Chrome 缓冲区错误漏洞 — Chrome--2026-07-01
CVE-2026-14385 Google Chrome 缓冲区错误漏洞 — Chrome--2026-07-01
CVE-2025-15666 Open Asset Import Library Assimp Model File SceneCombiner.cpp Copy heap-based overflow — Assimp 5.3 Medium2026-07-01
CVE-2026-20462 MediaTek chipset 缓冲区错误漏洞 — MediaTek chipset--2026-07-01

Vulnerabilities classified as CWE-122 (堆缓冲区溢出) represent 2169 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.