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-5272 Google Chrome 安全漏洞 — Chrome 8.8 -2026-04-01
CVE-2026-5275 Google Chrome 安全漏洞 — Chrome 8.8 -2026-04-01
CVE-2026-5236 Axiomatic Bento4 DSI v1 Ap4Dac4Atom.cpp SkipBits heap-based overflow — Bento4 5.3 Medium2026-03-31
CVE-2026-5235 Axiomatic Bento4 MP4 File Ap4Dac4Atom.cpp ReadCache heap-based overflow — Bento4 5.3 Medium2026-03-31
CVE-2026-34540 iccDEV: HBO in icMemDump() — iccDEV 6.2 Medium2026-03-31
CVE-2026-34539 iccDEV: HBO in CTiffImg::WriteLine() — iccDEV 6.2 Medium2026-03-31
CVE-2026-34535 iccDEV: SEGV in CIccTagArray::Cleanup() — iccDEV 6.2 Medium2026-03-31
CVE-2026-34534 iccDEV: HBO in CIccMpeSpectralMatrix::Describe() — iccDEV 6.2 Medium2026-03-31
CVE-2026-5201 Gdk-pixbuf: gdk-pixbuf: denial of service via heap-based buffer overflow when processing a specially crafted jpeg image — Red Hat Enterprise Linux 10 7.5 High2026-03-31
CVE-2026-5185 Nothings stb_image Multi-frame GIF File stb_image.h stbi__gif_load_next heap-based overflow — stb_image 5.3 Medium2026-03-31
CVE-2026-33987 FreeRDP: Persistent Cache bmpSize Desync - Heap OOB Write — FreeRDP 7.1 High2026-03-30
CVE-2026-33986 FreeRDP: H.264 YUV Buffer Dimension Desync - Heap OOB Write — FreeRDP 7.5 High2026-03-30
CVE-2026-33984 FreeRDP: ClearCodec resize_vbar_entry() Heap OOB Write — FreeRDP 7.5 High2026-03-30
CVE-2026-26073 EVerest: OCPP 1.6 heap corruption caused by lock-free insertion in event_queue — everest-core 5.9 Medium2026-03-26
CVE-2026-27654 NGINX ngx_http_dav_module vulnerability — NGINX Open Source 8.2 High2026-03-24
CVE-2026-4675 Google Chrome 缓冲区错误漏洞 — Chrome 8.1 -2026-03-24
CVE-2026-4673 Google Chrome 缓冲区错误漏洞 — Chrome 8.8 -2026-03-24
CVE-2026-33298 llama.cpp has a Heap Buffer Overflow via Integer Overflow in GGUF Tensor Parsing — llama.cpp 7.8 High2026-03-24
CVE-2026-33164 NULL Pointer Dereference in libde265 — libde265 7.5 -2026-03-20
CVE-2026-32710 Heap-based Buffer Overflow in MariaDB — server 8.6 High2026-03-20
CVE-2026-32945 PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser — pjproject 9.1 -2026-03-20
CVE-2026-4463 Google Chrome 安全漏洞 — Chrome 8.8 -2026-03-20
CVE-2026-4455 Google Chrome 安全漏洞 — Chrome 8.8 -2026-03-20
CVE-2026-4448 Google Chrome 安全漏洞 — Chrome 8.8 -2026-03-20
CVE-2026-4443 Google Chrome 安全漏洞 — Chrome 8.8 -2026-03-20
CVE-2026-4442 Google Chrome 安全漏洞 — Chrome 8.8 -2026-03-20
CVE-2026-3229 Integer Overflow in Certificate Chain Allocation — wolfSSL 9.8 -2026-03-19
CVE-2026-4395 Heap-based buffer overflow in wc_ecc_import_x963_ex KCAPI path — wolfssl 9.1 -2026-03-19
CVE-2026-3549 ECH parsing heap buffer overflow — wolfSSL 9.1 -2026-03-19
CVE-2026-2646 Heap buffer overflow in session parsing with wolfSSL_d2i_SSL_SESSION() function — wolfssl 8.1 -2026-03-19

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