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-23534 FreeRDP has heap-buffer-overflow in clear_decompress_bands_data — FreeRDP 9.8 -2026-01-19
CVE-2026-23533 FreeRDP has heap-buffer-overflow in clear_decompress_residual_data — FreeRDP 9.8 -2026-01-19
CVE-2026-23532 FreeRDP has heap-buffer-overflow in gdi_SurfaceToSurface — FreeRDP 9.8 -2026-01-19
CVE-2026-23531 FreeRDP has heap-buffer-overflow in clear_decompress — FreeRDP 9.8 -2026-01-19
CVE-2026-23530 FreeRDP has heap-buffer-overflow in planar_decompress_plane_rle — FreeRDP 9.8 -2026-01-19
CVE-2026-1145 quickjs-ng quickjs quickjs.c js_typed_array_constructor_ta heap-based overflow — quickjs 6.3 Medium2026-01-19
CVE-2025-15537 Mapnik dbfile.cpp string_value heap-based overflow — Mapnik 5.3 Medium2026-01-18
CVE-2025-15536 BYVoid OpenCC MaxMatchSegmentation.cpp MaxMatchSegmentation heap-based overflow — OpenCC 5.3 Medium2026-01-18
CVE-2025-15533 raysan5 raylib rtext.c GenImageFontAtlas heap-based overflow — raylib 5.3 Medium2026-01-18
CVE-2026-22854 FreeRDP has a heap-buffer-overflow in drive_process_irp_read — FreeRDP 9.8 -2026-01-14
CVE-2026-21283 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2026-01-13
CVE-2026-21281 InCopy | Heap-based Buffer Overflow (CWE-122) — InCopy 7.8 High2026-01-13
CVE-2026-21304 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-01-13
CVE-2026-21277 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2026-01-13
CVE-2026-20868 Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability — Windows 10 Version 1607 8.8 High2026-01-13
CVE-2026-20922 Windows NTFS Remote Code Execution Vulnerability — Windows 10 Version 1607 7.8 High2026-01-13
CVE-2026-20876 Windows Virtualization-Based Security (VBS) Enclave Elevation of Privilege Vulnerability — Windows 11 version 22H3 6.7 Medium2026-01-13
CVE-2026-20864 Windows Connected Devices Platform Service Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2026-01-13
CVE-2026-20840 Windows NTFS Remote Code Execution Vulnerability — Windows 10 Version 1607 7.8 High2026-01-13
CVE-2026-20837 Windows Media Remote Code Execution Vulnerability — Windows 10 Version 1809 7.8 High2026-01-13
CVE-2026-20820 Windows Common Log File System Driver Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-01-13
CVE-2025-25249 Fortinet多款产品 安全漏洞 — FortiSwitchManager 7.4 High2026-01-13
CVE-2026-0822 quickjs-ng quickjs quickjs.c js_typed_array_sort heap-based overflow — quickjs 6.3 Medium2026-01-10
CVE-2026-0821 quickjs-ng quickjs quickjs.c js_typed_array_constructor heap-based overflow — quickjs 7.3 High2026-01-10
CVE-2026-22697 CryptoLib Has Heap Buffer Overflow Vulnerability in KMC Base64 Decode Handling (KMC JSON base64ciphertext/base64cleartext) — CryptoLib 7.5 High2026-01-10
CVE-2026-22027 CryptoLib Vulnerable to Heap Buffer Overflow in MariaDB SA Hexstring Conversion — CryptoLib 9.8 -2026-01-10
CVE-2025-46643 Dell PowerProtect Data Domain 安全漏洞 — PowerProtect Data Domain with Data Domain Operating System (DD OS) Feature Release 2.3 Low2026-01-09
CVE-2026-21504 Heap Buffer Overflow in iccDEV ToneMap Parser — iccDEV 6.6 Medium2026-01-07
CVE-2026-21491 iccDEV has unicode buffer overflow in CIccTagTextDescription — iccDEV 6.1 Medium2026-01-06
CVE-2026-21490 iccDEV has heap buffer overflow in CIccTagLut16::Validate() — iccDEV 6.1 Medium2026-01-06

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