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-3354 IBM Tivoli Monitoring code execution — Tivoli Monitoring 8.1 High2025-08-06
CVE-2025-3320 IBM Tivoli Monitoring code execution — Tivoli Monitoring 8.1 High2025-08-06
CVE-2025-23317 NVIDIA Triton Inference Server 安全漏洞 — Triton Inference Server 9.1 Critical2025-08-06
CVE-2025-54630 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.8 Medium2025-08-06
CVE-2025-7033 Rockwell Automation Heap-based Buffer Overflow In Arena® Simulation — Arena® Simulation 7.8AIHighAI2025-08-05
CVE-2025-7025 Rockwell Automation Heap-based Buffer Overflow In Arena® Simulation — Arena® Simulation 7.8AIHighAI2025-08-05
CVE-2025-54574 Squid's URN Handling can lead to Buffer Overflow — squid 9.3 Critical2025-08-01
CVE-2025-48071 OpenEXR's Forged Unpacked Size can Lead to Heap-Based Buffer Overflow in Deep Scanline Parsing — openexr 7.8AIHighAI2025-07-31
CVE-2025-5043 3DM File Parsing Heap-Based Overflow Vulnerability — Shared Components 7.8 High2025-07-29
CVE-2025-8178 Tenda AC10 RequestsProcessLaid heap-based overflow — AC10 8.8 High2025-07-26
CVE-2025-40597 SonicWall SMA 100 Series 安全漏洞 — SMA 100 Series 9.8 -2025-07-23
CVE-2025-4657 Lenovo Protection Driver 安全漏洞 — PC Manager 6.7 Medium2025-07-17
CVE-2025-53816 GHSL-2025-058 - 7-Zip Multi-byte write heap buffer overflow in NCompress::NRar5::CDecoder — 7-Zip 6.2AIMediumAI2025-07-17
CVE-2025-24477 Fortinet FortiOS 安全漏洞 — FortiOS 4.0 Medium2025-07-15
CVE-2025-7545 GNU Binutils objcopy.c copy_section heap-based overflow — Binutils 5.3 Medium2025-07-13
CVE-2025-53630 Integer Overflow in GGUF Parser can lead to Heap Out-of-Bounds Read/Write in gguf — llama.cpp 9.8AICriticalAI2025-07-10
CVE-2025-5040 RTE File Parsing Heap-Based Overflow Vulnerability — Revit 7.8 High2025-07-10
CVE-2025-32990 Gnutls: vulnerability in gnutls certtool template parsing 6.5 Medium2025-07-10
CVE-2025-7208 9fans plan9port x509.c edump heap-based overflow — plan9port 5.5 Medium2025-07-09
CVE-2025-7207 mruby nregs codegen.c scope_new heap-based overflow — mruby 3.3 Low2025-07-09
CVE-2025-47099 InCopy | Heap-based Buffer Overflow (CWE-122) — InCopy 7.8 High2025-07-08
CVE-2025-47131 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2025-07-08
CVE-2025-47122 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2025-07-08
CVE-2025-47125 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2025-07-08
CVE-2025-47123 Adobe Framemaker | Heap-based Buffer Overflow (CWE-122) — Adobe Framemaker 7.8 High2025-07-08
CVE-2025-43591 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2025-07-08
CVE-2025-47134 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2025-07-08
CVE-2025-47103 InDesign Desktop | Heap-based Buffer Overflow (CWE-122) — InDesign Desktop 7.8 High2025-07-08
CVE-2025-43582 Substance3D - Viewer | Heap-based Buffer Overflow (CWE-122) — Substance3D - Viewer 7.8 High2025-07-08
CVE-2025-49744 Windows Graphics Component Elevation of Privilege Vulnerability — Windows 10 Version 1507 7.0 High2025-07-08

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