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-53182 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.5 Medium2025-07-07
CVE-2025-53181 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.5 Medium2025-07-07
CVE-2025-53180 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.5 Medium2025-07-07
CVE-2025-53179 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.5 Medium2025-07-07
CVE-2025-7069 HDF5 H5FSsection.c H5FS__sect_link_size heap-based overflow — HDF5 3.3 Low2025-07-04
CVE-2025-7067 HDF5 H5FScache.c H5FS__sinfo_serialize_node_cb heap-based overflow — HDF5 3.3 Low2025-07-04
CVE-2025-48379 Pillow Vulnerable to Write Buffer Overflow on BCn encoding — Pillow 7.1 High2025-07-01
CVE-2024-46993 Electron Vulnerable to Heap Buffer Overflow in NativeImage::CreateFromPath — electron 8.0AIHighAI2025-07-01
CVE-2023-28905 Heap buffer overflow in picserver — Volkswagen MIB3 infotainment system MIB3 OI MQB 8.0 High2025-06-28
CVE-2025-6818 HDF5 H5Ochunk.c H5O__chunk_protect heap-based overflow — HDF5 3.3 Low2025-06-28
CVE-2025-6816 HDF5 H5Ofsinfo.c H5O__fsinfo_encode heap-based overflow — HDF5 3.3 Low2025-06-28
CVE-2025-6750 HDF5 H5Omtime.c H5O__mtime_new_encode heap-based overflow — HDF5 3.3 Low2025-06-27
CVE-2025-6660 PDF-XChange Editor GIF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — PDF-XChange Editor 7.8AIHighAI2025-06-25
CVE-2025-5830 Autel MaxiCharger AC Wallbox Commercial DLB_SlaveRegister Heap-based Buffer Overflow Remote Code Execution Vulnerability — Autel MaxiCharger AC Wallbox Commercial 8.8AIHighAI2025-06-25
CVE-2025-6516 HDF5 H5Fint.c H5F_addr_decode_len heap-based overflow — HDF5 5.3 Medium2025-06-23
CVE-2025-6499 vstakhov libucl ucl_parser.c ucl_parse_multiline_string heap-based overflow — libucl 3.3 Low2025-06-23
CVE-2025-6494 sparklemotion nokogiri hashmap.c hashmap_get_with_hash heap-based overflow — nokogiri 3.3 Low2025-06-22
CVE-2025-6490 sparklemotion nokogiri hashmap.c hashmap_set_with_hash heap-based overflow — nokogiri 3.3 Low2025-06-22
CVE-2025-5477 Sony XAV-AX8500 Bluetooth L2CAP Protocol Heap-based Buffer Overflow Remote Code Execution Vulnerability — XAV-AX8500 8.8AIHighAI2025-06-21
CVE-2025-5479 Sony XAV-AX8500 Bluetooth AVCTP Protocol Heap-based Buffer Overflow Remote Code Execution Vulnerability — XAV-AX8500 8.8AIHighAI2025-06-21
CVE-2025-50054 OpenVPN ovpn-dco-win 安全漏洞 — ovpn-dco-win 5.5AIMediumAI2025-06-20
CVE-2025-6270 HDF5 H5FSsection.c H5FS__sect_find_node heap-based overflow — HDF5 5.3 Medium2025-06-19
CVE-2025-6269 HDF5 H5Cimage.c H5C__reconstruct_cache_entry heap-based overflow — HDF5 5.3 Medium2025-06-19
CVE-2025-20260 ClamAV PDF Scanning Buffer Overflow Vulnerability — ClamAV 9.8 Critical2025-06-18
CVE-2025-49850 Out-of-bounds Read in Write in LS Electric GMWin 4 — GMWin 4 7.8AIHighAI2025-06-17
CVE-2025-6120 Open Asset Import Library Assimp HL1MDLLoader.cpp read_meshes heap-based overflow — Assimp 5.3 Medium2025-06-16
CVE-2025-32717 Microsoft Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 8.4 High2025-06-10
CVE-2025-47107 InCopy | Heap-based Buffer Overflow (CWE-122) — InCopy 7.8 High2025-06-10
CVE-2025-47174 Microsoft Excel Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High2025-06-10
CVE-2025-47169 Microsoft Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High2025-06-10

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