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-2022-40661 Nikon NIS-Elements Viewer 安全漏洞 — NIS-Elements Viewer 7.8 -2022-09-15
CVE-2022-40660 Nikon NIS-Elements Viewer 安全漏洞 — NIS-Elements Viewer 7.8 -2022-09-15
CVE-2022-40655 Nikon NIS-Elements Viewer 缓冲区错误漏洞 — NIS-Elements Viewer 7.8 -2022-09-15
CVE-2022-36858 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36842 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36843 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36844 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36846 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36860 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36862 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36863 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36841 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-36845 SAMSUNG Mobile devices 缓冲区错误漏洞 — Samsung Mobile Devices 4.4 Medium2022-09-09
CVE-2022-38701 IPC in communication subsystem has a heap overflow vulnerability. Local attackers can trigger a heap overflow and get network sensitive information. — OpenHarmony 6.2 Medium2022-09-09
CVE-2022-25309 fribidi 缓冲区错误漏洞 — fribidi 5.5 -2022-09-06
CVE-2022-2915 SonicWALL SMA100 缓冲区错误漏洞 — SMA100 8.8 -2022-08-26
CVE-2022-2991 Linux kernel 缓冲区错误漏洞 — kernel 6.4 -2022-08-25
CVE-2022-26061 HDF5 Group libhdf5 缓冲区错误漏洞 — libhdf5 7.8 -2022-08-22
CVE-2022-2849 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-08-17
CVE-2022-2819 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-08-15
CVE-2022-35676 Adobe FrameMaker SVG File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — FrameMaker 7.8 High2022-08-11
CVE-2022-35677 Adobe FrameMaker SVG File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — FrameMaker 7.8 High2022-08-11
CVE-2022-2580 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-08-01
CVE-2022-2571 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-08-01
CVE-2022-2522 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-07-25
CVE-2022-31144 Potential heap overflow in Redis — redis 7.0 High2022-07-19
CVE-2022-1924 GStreamer 输入验证错误漏洞 — GStreamer 7.8 -2022-07-19
CVE-2022-1923 GStreamer 输入验证错误漏洞 — GStreamer 7.8 -2022-07-19
CVE-2022-2122 GStreamer 输入验证错误漏洞 — GStreamer 7.8 -2022-07-19
CVE-2022-1925 GStreamer 输入验证错误漏洞 — GStreamer 7.8 -2022-07-19

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