Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-122 (堆缓冲区溢出) — Vulnerability Class 1864

1864 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-2023-21692 Microsoft Protected Extensible Authentication Protocol (PEAP) Remote Code Execution Vulnerability — Windows 10 Version 1809 9.8 Critical2023-02-14
CVE-2023-21690 Microsoft Protected Extensible Authentication Protocol (PEAP) Remote Code Execution Vulnerability — Windows 10 Version 1809 9.8 Critical2023-02-14
CVE-2023-21689 Microsoft Protected Extensible Authentication Protocol (PEAP) Remote Code Execution Vulnerability — Windows 10 Version 1809 9.8 Critical2023-02-14
CVE-2023-21812 Windows Common Log File System Driver Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2023-02-14
CVE-2023-21804 Windows Graphics Component Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2023-02-14
CVE-2023-21799 Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability — Windows 10 Version 1809 8.8 High2023-02-14
CVE-2023-23378 Print 3D Remote Code Execution Vulnerability — Print 3D 7.8 High2023-02-14
CVE-2023-21528 Microsoft SQL Server Remote Code Execution Vulnerability — Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack 7.8 High2023-02-14
CVE-2023-24551 Siemens Solid Edge 安全漏洞 — Solid Edge SE2022 7.8 High2023-02-14
CVE-2023-24550 Siemens Solid Edge 安全漏洞 — Solid Edge SE2022 7.8 High2023-02-14
CVE-2023-0819 Heap-based Buffer Overflow in gpac/gpac — gpac/gpac 7.8 -2023-02-13
CVE-2022-34454 Dell PowerScale OneFS 缓冲区错误漏洞 — PowerScale OneFS 6.7 Medium2023-02-10
CVE-2023-0760 Heap-based Buffer Overflow in gpac/gpac — gpac/gpac 7.8 -2023-02-09
CVE-2022-34400 Dell BIOS 缓冲区错误漏洞 — CPG BIOS 7.1 High2023-02-01
CVE-2023-23582 Snap One Wattbox 缓冲区错误漏洞 — Wattbox WB-300-IP-3 5.3 Medium2023-01-30
CVE-2022-41991 Siretta QUARTZ-GOLD 缓冲区错误漏洞 — QUARTZ-GOLD 9.8 -2023-01-26
CVE-2022-42403 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42405 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-1892 Lenovo Notebook 安全漏洞 — BIOS 6.7 Medium2023-01-23
CVE-2022-1891 Lenovo Notebook 安全漏洞 — BIOS 6.7 Medium2023-01-23
CVE-2022-1890 Lenovo Notebook 缓冲区错误漏洞 — BIOS 6.7 Medium2023-01-23
CVE-2023-0433 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2023-01-21
CVE-2023-21605 Adobe Acrobat Reader DC Font Parsing Heap-based Buffer Overflow Arbitrary code execution — Acrobat Reader 7.8 High2023-01-18
CVE-2022-3160 Siemens Teamcenter Visualization 和 JT2Go 缓冲区错误漏洞 — JT2Go 7.8 High2023-01-13
CVE-2023-0288 Heap-based Buffer Overflow in vim/vim — vim/vim 7.8 -2023-01-13
CVE-2023-21587 Adobe InDesign Font Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — InDesign 7.8 High2023-01-13
CVE-2023-21594 Adobe InCopy Font Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — InCopy 7.8 High2023-01-13
CVE-2022-43591 Qt 安全漏洞 — Qt 8.8 -2023-01-12
CVE-2022-3437 Heimdal GSSAPI 安全漏洞 — samba 6.5 -2023-01-12
CVE-2021-3966 Usb bluetooth device ACL read cb buffer overflow — zephyr 9.6 Critical2023-01-11

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