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-2021-38439 GurumDDS Heap-based Buffer Overflow — GurumDDS 8.6 High2022-05-05
CVE-2022-20737 Cisco Adaptive Security Appliance Software Clientless SSL VPN Heap Overflow Vulnerability — Cisco Adaptive Security Appliance (ASA) Software 8.5 High2022-05-03
CVE-2022-1437 Heap-based Buffer Overflow in radareorg/radare2 — radareorg/radare2 7.1 -2022-04-22
CVE-2022-1383 Heap-based Buffer Overflow in radareorg/radare2 — radareorg/radare2 7.1 -2022-04-17
CVE-2022-1381 global heap buffer overflow in skip_range in vim/vim — vim/vim 7.8 -2022-04-17
CVE-2021-40426 Sound Exchange libsox 缓冲区错误漏洞 — libsox 8.8 -2022-04-14
CVE-2021-21948 AnyCubic Chitubox AnyCubic Plugin 输入验证错误漏洞 — Chitubox AnyCubic Plugin 7.8 -2022-04-14
CVE-2021-21947 Accusoft ImageGear 输入验证错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2021-21946 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2021-21945 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2021-21944 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2021-21943 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2021-21942 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2021-21914 Accusoft ImageGear 输入验证错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2022-21214 ICSA-22-090-03 Fuji Electric Alpha5 — Alpha5 7.8 High2022-04-12
CVE-2022-27572 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 8.1 High2022-04-11
CVE-2022-27571 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 8.1 High2022-04-11
CVE-2022-27570 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 8.1 High2022-04-11
CVE-2022-27568 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 8.1 High2022-04-11
CVE-2022-27569 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 8.1 High2022-04-11
CVE-2022-26098 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 8.1 High2022-04-11
CVE-2022-26092 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 7.4 High2022-04-11
CVE-2022-1286 heap-buffer-overflow in mrb_vm_exec in mruby/mruby in mruby/mruby — mruby/mruby 8.4 -2022-04-10
CVE-2022-1240 Heap buffer overflow in libr/bin/format/mach0/mach0.c in radareorg/radare2 — radareorg/radare2 7.8 -2022-04-06
CVE-2022-1253 Heap-based Buffer Overflow in strukturag/libde265 — strukturag/libde265 9.8 -2022-04-06
CVE-2022-1244 heap-buffer-overflow in radareorg/radare2 — radareorg/radare2 5.5 -2022-04-05
CVE-2022-24795 Buffer Overflow and Integer Overflow in yajl-ruby — yajl-ruby 5.9 Medium2022-04-05
CVE-2022-1160 heap buffer overflow in get_one_sourceline in vim/vim — vim/vim 7.8 -2022-03-30
CVE-2022-1052 Heap Buffer Overflow in iterate_chained_fixups in radareorg/radare2 — radareorg/radare2 6.2 -2022-03-24
CVE-2022-1061 Heap Buffer Overflow in parseDragons in radareorg/radare2 — radareorg/radare2 6.5 -2022-03-24

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