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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1859 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-40310 ImageMagick: Heap out-of-bounds write in JP2 encoder — ImageMagick 5.5 Medium2026-04-13
CVE-2026-40183 ImageMagick: Heap buffer overflow when encoding JXL image with a 16-bit float — ImageMagick 5.5 Medium2026-04-13
CVE-2026-40169 ImageMagick: Heap buffer overflow (WRITE) in the YAML and JSON encoders — ImageMagick 6.2 Medium2026-04-13
CVE-2026-33901 ImageMagick has a Heap Buffer Overflow via MVG decoder — ImageMagick 7.5 High2026-04-13
CVE-2026-33899 ImageMagick: Heap BufferOverflow write of single zero byte when parsing XML — ImageMagick 5.3 Medium2026-04-13
CVE-2026-32316 jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow — jq 8.2 High2026-04-13
CVE-2026-34865 Huawei HarmonyOS 安全漏洞 — HarmonyOS 9.1 -2026-04-13
CVE-2026-25205 SAMSUNG Escargot 安全漏洞 — Escargot 7.4 High2026-04-13
CVE-2026-4153 GIMP PSP File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — GIMP 7.8AIHighAI2026-04-11
CVE-2026-4152 GIMP JP2 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — GIMP 7.8AIHighAI2026-04-11
CVE-2026-29043 HDF5 H5T__ref_mem_setnull Heap Buffer Overflow — hdf5 5.5 Medium2026-04-10
CVE-2026-5448 1-2 Byte Buffer Overflow in wolfSSL_X509_notAfter/notBefore — wolfSSL 8.1 -2026-04-09
CVE-2026-5264 DTLS 1.3 ACK heap buffer overflow — wolfSSL 9.8AICriticalAI2026-04-09
CVE-2026-5447 Heap buffer overflow in CertFromX509() via AuthorityKeyIdentifier — wolfSSL 9.8AICriticalAI2026-04-09
CVE-2026-5187 Heap Out-of-Bounds Write in DecodeObjectId() in wolfSSL — wolfSSL 8.4AIHighAI2026-04-09
CVE-2026-5869 Google Chrome 安全漏洞 — Chrome 6.5AIMediumAI2026-04-08
CVE-2026-5868 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2026-04-08
CVE-2026-5867 Google Chrome 安全漏洞 — Chrome 6.5AIMediumAI2026-04-08
CVE-2026-5864 Google Chrome 安全漏洞 — Chrome 6.5AIMediumAI2026-04-08
CVE-2026-5858 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2026-04-08
CVE-2026-35199 SymCrypt SymCryptXmssSign function - Heap overflow via 64->32-bit leaf-count truncation — SymCrypt 6.1 Medium2026-04-06
CVE-2026-21372 Heap-Based Buffer Overflow in Power Management IC — Snapdragon 7.8 High2026-04-06
CVE-2026-34979 OpenPrinting CUPS: Heap overflow in `get_options()` — cups 5.3 Medium2026-04-03
CVE-2026-5474 NASA cFS CCSDS Packet Header to_lab_passthru_encode.c CFE_MSG_GetSize heap-based overflow — cFS 6.3 Medium2026-04-03
CVE-2026-34743 XZ Utils: Buffer overflow in lzma_index_append() — xz 7.5AIHighAI2026-04-02
CVE-2026-34120 Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C520WS — Tapo C520WS v2.6 6.5AIMediumAI2026-04-02
CVE-2026-34119 Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C520WS — Tapo C520WS v2.6 6.5AIMediumAI2026-04-02
CVE-2026-34118 Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C520WS — Tapo C520WS v2.6 6.5AIMediumAI2026-04-02
CVE-2026-5244 Cesanta Mongoose TLS 1.3 mongoose.c mg_tls_recv_cert heap-based overflow — Mongoose 7.3 High2026-04-02
CVE-2026-34545 OpenEXR: integer overflow lead to OOB in HTJ2K decoder — openexr 9.6AICriticalAI2026-04-01

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