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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1924 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-4391 TeamSpeak 3 Server ECC Key heap-based overflow — TeamSpeak 3 Server 5.3 Medium2026-05-27
CVE-2026-8175 Multiple vulnerabilities in Aspera applications. — Aspera High-Speed Transfer Endpoint 9.8 Critical2026-05-27
CVE-2026-9605 GNU libredwg Dwgbmp Utility bits.c bit_read_RC heap-based overflow — libredwg 7.3 High2026-05-26
CVE-2026-44983 smallbitvec: Safe API Triggered Heap Buffer Overflow via Integer Overflow — smallbitvec 7.3 High2026-05-26
CVE-2026-8834 IBM HTTP Server is affected by multiple vulnerabilities — HTTP Server 8.0 High2026-05-26
CVE-2026-40033 FreeRDP - Heap-buffer-overflow in gdi_CacheToSurface via rectangle validation bypass — FreeRDP 8.8 High2026-05-26
CVE-2026-48135 HTTP service can incorrectly process malformed HTTP requests — Quantum Security Gateway 5.3 Medium2026-05-26
CVE-2026-48131 VPND IKE Fragment Reassembly - Heap Out-of-Bounds Write via Sequence Number Zero — Quantum Security Gateway 8.1 High2026-05-26
CVE-2026-9541 Squirrel Cnut File sqobject.cpp ReadObject heap-based overflow — Squirrel 5.3 Medium2026-05-26
CVE-2026-7310 HiDraw XML解析器堆溢出漏洞 — MACH HiDraw--2026-05-26
CVE-2026-25713 MediaInfoLib ID3v2解析堆缓冲区溢出漏洞 — MediaInfoLib 7.8 High2026-05-26
CVE-2026-9502 GNU LibreDWG Dwgread Utility decode.c decompress_R2004_section heap-based overflow — LibreDWG 5.3 Medium2026-05-25
CVE-2026-9500 GNU LibreDWG Dwgread Utility decode.c read_2004_compressed_section heap-based overflow — LibreDWG 5.3 Medium2026-05-25
CVE-2026-9365 Ettercap GG Dissector ec_gg.c FUNC_DECODER heap-based overflow — Ettercap 5.6 Medium2026-05-24
CVE-2026-9256 NGINX ngx_http_rewrite_module vulnerability — NGINX Plus 8.1 High2026-05-22
CVE-2026-8997 Heap Buffer Overflow in vifm — vifm--2026-05-22
CVE-2026-45252 Heap overflow in FUSE_LISTXATTR — FreeBSD--2026-05-21
CVE-2026-44050 Heap buffer overflow in CNID daemon comm_rcv() — Netatalk 9.9 Critical2026-05-21
CVE-2026-9149 Libsolv: heap buffer overflow in libsolv repo_add_solv via negative maxsize from crafted .solv file — Red Hat Enterprise Linux 10 6.5 Medium2026-05-20
CVE-2026-8631 HP Linux Imaging and Printing Software – Potential Escalation of Privilege and Arbitrary Code Execution — HP Linux Imaging and Printing Software--2026-05-20
CVE-2026-9123 Google Chrome 安全漏洞 — Chrome--2026-05-20
CVE-2026-9119 Google Chrome 安全漏洞 — Chrome--2026-05-20
CVE-2026-22554 MediaInfoLib 安全漏洞 — MediaInfoLib 7.8 High2026-05-20
CVE-2026-45584 Microsoft Defender Remote Code Execution Vulnerability — Microsoft Malware Protection Engine 8.1 High2026-05-20
CVE-2026-32741 libheif has a heap buffer overflow in decode_mask_image() — libheif 7.1 High2026-05-19
CVE-2026-33633 Kitty has a Heap Buffer Overflow in its Graphics Protocol Handler — kitty 7.5 High2026-05-19
CVE-2026-8711 NGINX JavaScript vulnerability — NGINX JavaScript 8.1 High2026-05-19
CVE-2026-47311 SAMSUNG Escargot 安全漏洞 — Escargot 7.8 High2026-05-19
CVE-2026-44662 rust-openssl: Heap buffer overflow when encrypting with AES key-wrap-with-padding — rust-openssl--2026-05-14
CVE-2026-44636 libsixel: integer overflow in encoder — libsixel 7.4 High2026-05-14

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