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-2025-32401 RT-Labs P-Net 安全漏洞 — P-Net 4.8 Medium2025-05-07
CVE-2025-32400 RT-Labs P-Net 安全漏洞 — P-Net 7.5 High2025-05-07
CVE-2025-32397 RT-Labs P-Net 安全漏洞 — P-Net 7.5 High2025-05-07
CVE-2025-32396 RT-Labs P-Net 安全漏洞 — P-Net 7.5 High2025-05-07
CVE-2025-4355 Tenda DAP-1520 api set_ws_action heap-based overflow — DAP-1520 8.8 High2025-05-06
CVE-2025-4096 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2025-05-05
CVE-2024-6031 Tesla Model S oFono AT Command Heap-based Buffer Overflow Code Execution Vulnerability — Model S 8.4AIHighAI2025-04-30
CVE-2025-1049 Sonos Era 300 Heap-based Buffer Overflow Remote Code Execution Vulnerability — Era 300 8.8 -2025-04-23
CVE-2025-1045 Luxion KeyShot Viewer KSP File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — KeyShot Viewer 7.8 -2025-04-23
CVE-2025-3791 symisc UnQLite unqlite.c jx9MemObjStore heap-based overflow — UnQLite 5.3 Medium2025-04-18
CVE-2025-3619 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2025-04-16
CVE-2025-1656 PDF File Parsing Heap-based Overflow Vulnerability — Revit 7.8 High2025-04-15
CVE-2025-1273 PDF File Parsing Heap-Based Overflow Vulnerability — Revit 7.8 High2025-04-15
CVE-2025-2497 DWG File Parsing Stack-Based Buffer Vulnerability — Revit 7.8 High2025-04-15
CVE-2025-1275 JPG File Parsing Heap-Based Overflow Vulnerability — Revit 7.8 High2025-04-15
CVE-2025-3277 SQLite 安全漏洞 — sqlite 9.8AICriticalAI2025-04-14
CVE-2025-31344 The giflib open-source component has a buffer overflow vulnerability — giflib 7.3 High2025-04-14
CVE-2025-3549 Open Asset Import Library Assimp File MD3Loader.cpp ValidateSurfaceHeaderOffsets heap-based overflow — Assimp 5.3 Medium2025-04-14
CVE-2025-3548 Open Asset Import Library Assimp File types.h Set heap-based overflow — Assimp 5.3 Medium2025-04-14
CVE-2024-56406 Perl is vulnerable to a heap buffer overflow when transliterating non-ASCII bytes — perl 9.8AICriticalAI2025-04-13
CVE-2025-3512 Buffer overflow in QTextMarkdownImporter — Qt 9.1AICriticalAI2025-04-11
CVE-2025-30644 Junos OS: EX2300, EX3400, EX4000 Series, QFX5k Series: Receipt of a specific DHCP packet causes FPC crash when DHCP Option 82 is enabled — Junos OS 7.5 High2025-04-09
CVE-2025-30295 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2025-04-08
CVE-2025-30299 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2025-04-08
CVE-2025-27199 Animate | Heap-based Buffer Overflow (CWE-122) — Animate 7.8 High2025-04-08
CVE-2025-27198 Photoshop Desktop | Heap-based Buffer Overflow (CWE-122) — Photoshop Desktop 7.8 High2025-04-08
CVE-2025-27196 Premiere Pro | Heap-based Buffer Overflow (CWE-122) — Premiere Pro 7.8 High2025-04-08
CVE-2025-27193 Bridge | Heap-based Buffer Overflow (CWE-122) — Bridge 7.8 High2025-04-08
CVE-2025-27195 Media Encoder | Heap-based Buffer Overflow (CWE-122) — Media Encoder 7.8 High2025-04-08
CVE-2025-27490 Windows Bluetooth Service Elevation of Privilege Vulnerability — Windows 10 Version 21H2 7.8 High2025-04-08

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