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-45130 Vim: Heap Buffer Overflow in spell file loading — vim 6.6 Medium2026-05-08
CVE-2026-8087 OSGeo gdal GDapi.c GDnentries heap-based overflow — gdal 5.3 Medium2026-05-07
CVE-2026-8086 OSGeo gdal SWapi.c SWnentries heap-based overflow — gdal 5.3 Medium2026-05-07
CVE-2026-7900 Google Chrome 148.0.7778.7778 HEAPS缓冲区溢出漏洞 — Chrome--2026-05-06
CVE-2026-20185 Cisco SG350 and SG350X Series Managed Switches SNMP Denial of Service Vunerability — Cisco Small Business Smart and Managed Switches 7.7 High2026-05-06
CVE-2026-28780 Apache HTTP Server: buffer overflow in mod_proxy_ajp via ajp_msg_check_header() — Apache HTTP Server--2026-05-05
CVE-2026-25589 RedisBloom RESTORE invalid memory access may allow remote code execution — RedisBloom--2026-05-05
CVE-2026-25588 RedisTimeSeries RESTORE invalid memory access may allow remote code execution — RedisTimeSeries--2026-05-05
CVE-2026-25243 redis-server RESTORE invalid memory access may allow remote code execution — redis--2026-05-05
CVE-2026-29004 BusyBox DHCPv6 Client Heap Buffer Overflow via DNS_SERVERS — busybox_mirror 8.1 High2026-05-04
CVE-2026-5403 Heap-based Buffer Overflow in Wireshark — Wireshark 7.8 High2026-04-30
CVE-2026-5405 Heap-based Buffer Overflow in Wireshark — Wireshark 7.8 High2026-04-30
CVE-2026-35547 Heap overflow in libnv — FreeBSD 9.8AICriticalAI2026-04-30
CVE-2026-42512 Remotely triggerable out-of-bounds heap write in dhclient — FreeBSD 9.8AICriticalAI2026-04-30
CVE-2026-5402 Heap-based Buffer Overflow in Wireshark — Wireshark 8.8 High2026-04-30
CVE-2026-5653 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-04-30
CVE-2026-6530 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-04-30
CVE-2026-6529 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-04-30
CVE-2026-7378 Heap-based Buffer Overflow in Wireshark — Wireshark 5.5 Medium2026-04-30
CVE-2026-7339 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7353 Google Chrome 安全漏洞 — Chrome 9.6AICriticalAI2026-04-28
CVE-2026-20766 Milesight Cameras Heap-based Buffer Overflow — MS-Cxx63-PD 8.8 High2026-04-27
CVE-2026-6846 Binutils: binutils: arbitrary code execution via malformed xcoff object file processing — Red Hat Enterprise Linux 10 7.8 High2026-04-22
CVE-2026-40614 PJSIP: Heap buffer overflow in Opus codec decoding — pjproject 7.5AIHighAI2026-04-21
CVE-2026-40706 Tuxera NTFS-3G 安全漏洞 — NTFS-3G 8.4 High2026-04-21
CVE-2026-5450 scanf %mc off-by-one heap buffer overflow — glibc 9.8AICriticalAI2026-04-20
CVE-2026-32135 NanoMQ has Heap Buffer Overflow in URI Parameter Parsing — nanomq 9.8AICriticalAI2026-04-20
CVE-2026-32956 Silex SD-330AC和Silex AMC Manager 安全漏洞 — SD-330AC 9.8 Critical2026-04-20
CVE-2026-32961 Silex SD-330AC和Silex AMC Manager 安全漏洞 — SD-330AC 5.3 Medium2026-04-20
CVE-2026-35512 xrdp: Heap buffer overflow in EGFX channel — xrdp 9.8AICriticalAI2026-04-17

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