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-2019-18295 Siemens SPPA-T3000 缓冲区错误漏洞 — SPPA-T3000 MS3000 Migration Server 9.8 -2019-12-12
CVE-2019-18296 Siemens SPPA-T3000 缓冲区错误漏洞 — SPPA-T3000 MS3000 Migration Server 9.8 -2019-12-12
CVE-2019-18297 Siemens SPPA-T3000 缓冲区错误漏洞 — SPPA-T3000 MS3000 Migration Server 7.8 -2019-12-12
CVE-2019-5154 LEAD Technologies LEADTOOLS 缓冲区错误漏洞 — LEADTOOLS 8.8 -2019-12-11
CVE-2019-14895 Linux kernel 缓冲区错误漏洞 — kernel 9.8 -2019-11-29
CVE-2019-14896 Linux kernel 缓冲区错误漏洞 — kernel 9.8 -2019-11-27
CVE-2019-14815 Linux kernel 缓冲区错误漏洞 — kernel 7.8 -2019-11-25
CVE-2019-18240 Fuji Electric V-Server 缓冲区错误漏洞 — Fuji Electric V-Server 4.0.6 and prior 9.8 -2019-11-13
CVE-2019-5125 LEAD Technologies LEADTOOLS 缓冲区错误漏洞 — LEADTOOLS 8.8 -2019-11-06
CVE-2019-5030 Antenna House Rainbow PDF Office Server Document Converter 缓冲区错误漏洞 — Antenna House 8.4 -2019-10-31
CVE-2019-15679 TightVNC 缓冲区错误漏洞 — TightVNC 9.8 -2019-10-29
CVE-2019-15678 TightVNC 缓冲区错误漏洞 — TightVNC 9.8 -2019-10-29
CVE-2019-5046 Nitro Software NitroPDF 缓冲区错误漏洞 — NitroPDF 7.8 -2019-10-09
CVE-2019-5048 Nitro Software NitroPDF 缓冲区错误漏洞 — NitroPDF 7.8 -2019-10-09
CVE-2019-5050 Nitro Software NitroPDF 缓冲区错误漏洞 — NitroPDF 7.8 -2019-10-09
CVE-2019-5045 Nitro Software NitroPDF 缓冲区错误漏洞 — NitroPDF 7.8 -2019-10-09
CVE-2019-14814 Linux kernel 缓冲区错误漏洞 — kernel 7.8 -2019-09-20
CVE-2019-14816 Linux kernel 缓冲区错误漏洞 — kernel 7.8 -2019-09-20
CVE-2019-5482 HAXX libcurl 缓冲区错误漏洞 — curl 9.8 -2019-09-16
CVE-2019-13536 Delta Electronics TPEditor 缓冲区错误漏洞 — TPEditor 7.8 -2019-09-11
CVE-2019-5039 Openweave-core 缓冲区错误漏洞 — Nest Labs 8.8 -2019-08-20
CVE-2019-5058 SDL2_image 缓冲区错误漏洞 — SDL 8.8 -2019-07-31
CVE-2019-5057 SDL2_image 缓冲区错误漏洞 — SDL 8.8 -2019-07-31
CVE-2019-10982 Delta Electronics CNCSoft ScreenEditor 缓冲区错误漏洞 — CNCSoft ScreenEditor 7.8 -2019-07-24
CVE-2019-3570 Facebook HHVM 缓冲区错误漏洞 — HHVM 9.8 -2019-07-18
CVE-2019-10192 Redis Labs Redis hyperloglog 缓冲区错误漏洞 — redis 7.2 -2019-07-11
CVE-2019-10126 Linux kernel 缓冲区错误漏洞 — kernel 9.8 -2019-06-14
CVE-2019-6530 Panasonic FPWIN Pro 缓冲区错误漏洞 — FPWIN Pro 7.8 -2019-06-07
CVE-2019-3846 Linux kernel 缓冲区错误漏洞 — kernel 8.8 -2019-06-03
CVE-2019-6740 Samsung Galaxy S9 ASN.1解析器缓冲区错误漏洞 — Galaxy S9 8.8 -2019-06-03

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