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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1863 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-25576 ImageMagick: Out of bounds read in multiple coders read raw pixel data — ImageMagick 5.1 Medium2026-02-24
CVE-2025-69247 free5GC has Heap Buffer Overflow in UPF Leading to Denial of Service — go-upf 7.5AIHighAI2026-02-23
CVE-2025-14905 389-ds-base: 389-ds-base: remote code execution and denial of service via heap buffer overflow — Red Hat Directory Server 11.5 E4S for RHEL 8 7.2 High2026-02-23
CVE-2026-2913 libvips source.c vips_source_read_to_memory heap-based overflow — libvips 2.5 Low2026-02-22
CVE-2026-27168 SAIL: Heap-based Buffer Overflow in Sail-codecs-xwd — sail 8.8 High2026-02-20
CVE-2026-2047 GIMP ICNS File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — GIMP 7.8AIHighAI2026-02-20
CVE-2026-0797 GIMP ICO File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — GIMP 7.8AIHighAI2026-02-20
CVE-2026-26967 PJSIP has a Heap-based Buffer Overflow vulnerability in its H.264 unpacketizer — pjproject 9.8 -2026-02-20
CVE-2026-26200 HDF5 Affected by H5T__conv_struct_opt Heap Buffer Overflow — hdf5 7.8 High2026-02-19
CVE-2026-2650 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2026-02-18
CVE-2026-2648 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2026-02-18
CVE-2026-2661 Squirrel sqobject.h operator heap-based overflow — Squirrel 3.3 Low2026-02-18
CVE-2026-2653 admesh normals.c stl_check_normal_vector heap-based overflow — admesh 5.3 Medium2026-02-18
CVE-2026-2474 Crypt::URandom versions from 0.41 before 0.55 for Perl is vulnerable to a heap buffer overflow in the XS function crypt_urandom_getrandom() — Crypt::URandom 9.1AICriticalAI2026-02-16
CVE-2019-25327 Prime95 Version 29.8 build 6 - Buffer Overflow (SEH) — Prime95 9.8 Critical2026-02-12
CVE-2026-2007 PostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory — PostgreSQL 8.2 High2026-02-12
CVE-2026-2005 PostgreSQL pgcrypto heap buffer overflow executes arbitrary code — PostgreSQL 8.8 High2026-02-12
CVE-2026-2314 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2026-02-11
CVE-2025-57709 Qsync Central — Qsync Central 9.1AICriticalAI2026-02-11
CVE-2026-21358 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 5.5 Medium2026-02-10
CVE-2026-21357 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-02-10
CVE-2026-21239 Windows Kernel Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-02-10
CVE-2026-21245 Windows Kernel Elevation of Privilege Vulnerability — Windows 11 Version 24H2 7.8 High2026-02-10
CVE-2026-21244 Windows Hyper-V Remote Code Execution Vulnerability — Windows 10 Version 1607 7.3 High2026-02-10
CVE-2026-21236 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-02-10
CVE-2026-21246 Windows Graphics Component Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-02-10
CVE-2026-21248 Windows Hyper-V Remote Code Execution Vulnerability — Windows 10 Version 1607 7.3 High2026-02-10
CVE-2026-21259 Microsoft Excel Elevation of Privilege Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High2026-02-10
CVE-2026-25646 LIBPNG has a heap buffer overflow in png_set_quantize — libpng 7.5 -2026-02-10
CVE-2026-23719 Siemens Simcenter Femap和Siemens Simcenter Nastran 安全漏洞 — Simcenter Femap 7.8 High2026-02-10

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