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-2024-41147 Miniaudio 安全漏洞 — Miniaudio 7.7 High2025-03-04
CVE-2025-1788 rizinorg rizin utf8.c rz_utf8_encode heap-based overflow — rizin 5.3 Medium2025-03-01
CVE-2025-22881 Heap-based Buffer Overflow in CNCSoft-G2 — CNCSoft-G2 8.8 -2025-02-26
CVE-2024-27245 Zoom Workplace Apps and SDKs - Buffer Overflow — Zoom Workplace Apps and SDKs 4.3 Medium2025-02-25
CVE-2024-45421 Zoom Apps - Buffer Overflow — Zoom Apps 8.5 High2025-02-25
CVE-2025-1538 D-Link DAP-1320 api set_ws_action heap-based overflow — DAP-1320 8.8 High2025-02-21
CVE-2025-27091 OpenH264 Decoding Functions Heap Overflow Vulnerability — openh264 6.8 -2025-02-20
CVE-2025-1426 Google chrome 安全漏洞 — Chrome 8.8 -2025-02-19
CVE-2025-0999 Google chrome 安全漏洞 — Chrome 8.8 -2025-02-19
CVE-2025-0633 Heap Overflow in iniparser.c — iniparser 7.1 -2025-02-19
CVE-2024-0145 NVIDIA nvJPEG2000 安全漏洞 — nvJPEG2000 6.8 Medium2025-02-12
CVE-2025-0903 PDF-XChange Editor RTF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — PDF-XChange Editor 7.8 -2025-02-11
CVE-2025-1052 Mintty Sixel Image Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — Mintty 7.8 -2025-02-11
CVE-2025-21414 Windows Core Messaging Elevation of Privileges Vulnerability — Windows 10 Version 1507 7.0 High2025-02-11
CVE-2025-21184 Windows Core Messaging Elevation of Privileges Vulnerability — Windows 10 Version 1507 7.0 High2025-02-11
CVE-2025-21390 Microsoft Excel Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High2025-02-11
CVE-2025-21371 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-02-11
CVE-2025-21190 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-02-11
CVE-2025-21200 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-02-11
CVE-2025-21407 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-02-11
CVE-2025-21410 Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability — Windows Server 2008 R2 Service Pack 1 8.8 High2025-02-11
CVE-2025-21208 Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability — Windows Server 2008 R2 Service Pack 1 8.8 High2025-02-11
CVE-2025-21418 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability — Windows 10 Version 1507 7.8 High2025-02-11
CVE-2025-21369 Microsoft Digest Authentication Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-02-11
CVE-2025-21368 Microsoft Digest Authentication Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-02-11
CVE-2025-21123 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2025-02-11
CVE-2025-1176 GNU Binutils ld elflink.c _bfd_elf_gc_mark_rsec heap-based overflow — Binutils 5.0 Medium2025-02-11
CVE-2025-22880 Heap-based Buffer Overflow in CNCSoft-G2 — CNCSoft-G2 7.8 High2025-02-07
CVE-2023-40222 Ashlar-Vellum Cobalt, Xenon, Argon, Lithium Heap-based Buffer Overflow — Cobalt 7.8 High2025-02-04
CVE-2025-0870 Axiomatic Bento4 Ap4DataBuffer.h GetData heap-based overflow — Bento4 5.6 Medium2025-01-30

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