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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1864 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-2025-21306 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21302 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21303 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21282 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21266 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21252 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21248 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21239 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21241 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21237 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21236 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21233 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21171 .NET Remote Code Execution Vulnerability — .NET 9.0 7.5 High2025-01-14
CVE-2025-21413 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-21411 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-01-14
CVE-2025-22134 heap-buffer-overflow with visual mode in Vim < 9.1.1003 — vim 4.2 Medium2025-01-13
CVE-2024-56827 Openjpeg: heap buffer overflow in lib/openjp2/j2k.c 5.6 Medium2025-01-09
CVE-2024-56826 Openjpeg: heap buffer overflow in bin/common/color.c 5.6 Medium2025-01-09
CVE-2024-51737 RediSearch Integer Overflow with LIMIT or KNN arguments can lead to RCE — RediSearch 7.0 High2025-01-08
CVE-2024-51480 RedisTimeSeries Integer Overflow Remote Code Execution Vulnerability — RedisTimeSeries 7.0 High2025-01-08
CVE-2024-13051 Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — Graphite 7.8 -2024-12-30
CVE-2024-13050 Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — Graphite 7.8 -2024-12-30
CVE-2024-56737 GNU GRUB 安全漏洞 — GRUB2 9.8 -2024-12-29
CVE-2024-56732 HarfBuzz heap-buffer-overflow on hb_cairo_glyphs_from_buffer — harfbuzz 8.8 -2024-12-27
CVE-2020-12819 FortiOS 安全漏洞 — FortiOS 5.4 Medium2024-12-19
CVE-2024-12670 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12669 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12179 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-49775 Siemens Opcenter Execution Foundation 安全漏洞 — Opcenter Execution Foundation 9.8 Critical2024-12-16
CVE-2024-8798 Bluetooth: classic: avdtp: missing buffer length check — Zephyr 7.5 High2024-12-15

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