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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1990 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-48914 Qemu-kvm: heap buffer overflow in virtio-blk scsi request handling 6.7 Medium2026-06-12
CVE-2026-12030 Chrome Android <149.0.7827.115越界写入漏洞 — Chrome--2026-06-11
CVE-2026-12010 Android Chrome<149.0.7827.115 GPU堆溢出漏洞 — Chrome--2026-06-11
CVE-2026-53465 ImageMagick: Heap Buffer Over-Write in SF3 encoder when writing multi-frame image — ImageMagick 6.2 Medium2026-06-10
CVE-2026-48994 ImageMagick: Heap Buffer Over-Write in MAT decoder on 32-bit systems — ImageMagick 5.9 Medium2026-06-10
CVE-2026-46692 ImageMagick: Heap Buffer Over-Write in distributed pixel cache server — ImageMagick 4.1 Medium2026-06-10
CVE-2026-46520 ImageMagick: Heap Buffer Over-Write in IPL decoder when reading multiple images of different dimensions — ImageMagick 7.5 High2026-06-10
CVE-2026-2049 GIMP HDR File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — GIMP--2026-06-10
CVE-2026-11884 389-ds-base: 389-ds-base: heap buffer overflow in schema objectclass serialization due to missing oc_superior in size calculation — Red Hat Directory Server 11 6.5 Medium2026-06-10
CVE-2026-45542 ESF-IDF: Heap buffer overflow in protocomm Security2 over Bluetooth — esp-idf 7.1 High2026-06-10
CVE-2026-48291 Format Plugins | Heap-based Buffer Overflow (CWE-122) — Format Plugins 7.8 High2026-06-09
CVE-2026-48292 Format Plugins | Heap-based Buffer Overflow (CWE-122) — Format Plugins 7.8 High2026-06-09
CVE-2026-47952 Acrobat Reader | Heap-based Buffer Overflow (CWE-122) — Acrobat Reader 7.8 High2026-06-09
CVE-2026-11824 SQLite before 3.53.2 Heap Buffer Overflow via FTS5 fts5ChunkIterate — SQLite 7.8 High2026-06-09
CVE-2026-11822 SQLite before 3.53.2 Memory Corruption in FTS5 Extension — SQLite 7.8 High2026-06-09
CVE-2026-34707 InCopy | Heap-based Buffer Overflow (CWE-122) — InCopy 7.8 High2026-06-09
CVE-2026-34701 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-06-09
CVE-2026-34698 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-06-09
CVE-2026-34699 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-06-09
CVE-2026-42993 Remote Desktop Client Remote Code Execution Vulnerability — Windows 10 Version 21H2 7.5 High2026-06-09
CVE-2026-44799 Remote Desktop Client Remote Code Execution Vulnerability — Remote Desktop client for Windows Desktop 7.5 High2026-06-09
CVE-2026-44808 Windows DWM Core Library Elevation of Privilege Vulnerability — Windows 11 version 26H1 7.8 High2026-06-09
CVE-2026-44811 Windows DWM Core Library Elevation of Privilege Vulnerability — Windows 11 version 26H1 7.8 High2026-06-09
CVE-2026-42992 Remote Desktop Client Remote Code Execution Vulnerability — Windows 10 Version 1607 7.5 High2026-06-09
CVE-2026-42904 Windows TCP/IP Elevation of Privilege Vulnerability — Windows 10 Version 21H2 9.6 Critical2026-06-09
CVE-2026-48574 Windows Media Remote Code Execution Vulnerability — Windows 10 Version 1607 7.8 High2026-06-09
CVE-2026-45653 Windows Kernel Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.0 High2026-06-09
CVE-2026-45638 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-06-09
CVE-2026-45636 Windows NTFS Remote Code Execution Vulnerability — Windows 10 Version 1607 7.8 High2026-06-09
CVE-2026-47652 Windows Hyper-V Remote Code Execution Vulnerability — Windows 11 version 23H2 8.2 High2026-06-09

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