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

Goal: 1000 CNY · Raised: 1110 CNY

100%

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

1913 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-6306 Google Chrome 安全漏洞 — Chrome 8.8 -2026-04-15
CVE-2026-6298 Google Chrome 安全漏洞 — Chrome 6.5 -2026-04-15
CVE-2026-6296 Google Chrome 安全漏洞 — Chrome 9.6 -2026-04-15
CVE-2026-27301 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 5.5 Medium2026-04-14
CVE-2026-27293 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2026-04-14
CVE-2026-33020 libsixel: Integer Overflow in write_png_to_file() leads to Heap-based Buffer Overflow — libsixel 7.1 High2026-04-14
CVE-2026-34630 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2026-04-14
CVE-2026-27312 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2026-04-14
CVE-2026-27310 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2026-04-14
CVE-2026-27311 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2026-04-14
CVE-2026-27313 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2026-04-14
CVE-2026-34628 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-04-14
CVE-2026-34629 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-04-14
CVE-2026-34627 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-04-14
CVE-2026-26176 Windows Client Side Caching driver (csc.sys) Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-04-14
CVE-2026-26156 Windows Hyper-V Remote Code Execution Vulnerability — Windows 10 Version 1607 7.8 High2026-04-14
CVE-2026-32223 Windows USB Printing Stack (usbprint.sys) Elevation of Privilege Vulnerability — Windows 11 Version 24H2 6.8 Medium2026-04-14
CVE-2026-32221 Windows Graphics Component Remote Code Execution Vulnerability — Windows 11 Version 24H2 8.4 High2026-04-14
CVE-2026-32087 Windows Function Discovery Service (fdwsd.dll) Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.0 High2026-04-14
CVE-2026-26180 Windows Kernel Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-04-14
CVE-2026-27285 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 5.5 Medium2026-04-14
CVE-2026-27286 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 5.5 Medium2026-04-14
CVE-2026-27238 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-04-14
CVE-2026-22828 Fortinet FortiManager Cloud和Fortinet FortiAnalyzer Cloud 安全漏洞 — FortiAnalyzer Cloud 7.3 High2026-04-14
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

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