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-21017 Acrobat Reader DC Heap-based Buffer Overflow Vulnerability Could Lead To Arbitrary Code Execution — Acrobat Reader 8.8 High2021-02-11
CVE-2020-28595 Prusa Research PrusaSlicer 缓冲区错误漏洞 — Prusa Research 7.8 -2021-02-10
CVE-2020-13572 Accusoft ImageGear 缓冲区错误漏洞 — Accusoft 8.8 -2021-02-10
CVE-2020-27250 SoftMaker Office PlanMaker 缓冲区错误漏洞 — SoftMaker 7.8 -2021-02-10
CVE-2020-13581 SoftMaker Office PlanMaker 缓冲区错误漏洞 — SoftMaker 7.8 -2021-02-10
CVE-2020-17423 Foxit Studio Photo 缓冲区错误漏洞 — Studio Photo 7.8 -2021-02-09
CVE-2020-13586 SoftMaker Office PlanMaker 缓冲区错误漏洞 — Softmaker 7.8 -2021-02-04
CVE-2020-27249 SoftMaker Office PlanMaker 缓冲区错误漏洞 — Softmaker 7.8 -2021-02-04
CVE-2020-27248 SoftMaker Office PlanMaker 缓冲区错误漏洞 — Softmaker 7.8 -2021-02-04
CVE-2020-27247 SoftMaker Office PlanMaker 缓冲区错误漏洞 — Softmaker 7.8 -2021-02-04
CVE-2021-22641 Fuji Electric Tellus Lite V-Simulator和Fuji Electric V-Server Lite 缓冲区错误漏洞 — Tellus Lite V-Simulator and V-Server Lite 7.8 -2021-01-27
CVE-2020-27297 Honeywell OPC UA Tunneller 缓冲区错误漏洞 — OPC UA Tunneller 9.8 -2021-01-26
CVE-2020-27814 OpenJPEG 代码问题漏洞 — openjpeg 7.8 -2021-01-25
CVE-2020-25681 Dnsmasq 缓冲区错误漏洞 — dnsmasq 8.1 -2021-01-20
CVE-2020-25687 Dnsmasq 缓冲区错误漏洞 — dnsmasq 5.9 -2021-01-20
CVE-2020-25682 Dnsmasq 缓冲区错误漏洞 — dnsmasq 8.1 -2021-01-20
CVE-2020-25683 Dnsmasq 安全漏洞 — dnsmasq 7.4 -2021-01-20
CVE-2020-27263 Kepware Kepserverex 缓冲区错误漏洞 — PTC Kepware KEPServerEX 9.8 -2021-01-13
CVE-2021-21006 Heap buffer overflow when handling crafted font file could lead to arbitrary code execution — Photoshop 8.6 High2021-01-13
CVE-2020-26994 Siemens Jt2go和Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 -2021-01-12
CVE-2020-26985 Siemens Jt2go和Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 8.8 -2021-01-12
CVE-2020-26986 Siemens Jt2go和Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 8.8 -2021-01-12
CVE-2020-26987 Siemens Jt2go和Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 8.8 -2021-01-12
CVE-2020-15800 SCALANCE X-200IRT 缓冲区错误漏洞 — SCALANCE X-200 switch family (incl. SIPLUS NET variants) 9.8 -2021-01-12
CVE-2020-25226 Siemens SCALANCE X-200IRT 缓冲区错误漏洞 — SCALANCE X-200 switch family (incl. SIPLUS NET variants) 9.8 -2021-01-12
CVE-2020-27841 OpenJPEG 缓冲区错误漏洞 — openjpeg 5.5 -2021-01-05
CVE-2020-25843 CHANGING Inc. NHIServiSignAdapter Windows Versions - Heap Overflow — NHIServiSignAdapter 8.1 High2020-12-31
CVE-2020-25712 xorg-x11-server 缓冲区错误漏洞 — xorg-x11-server 7.8 -2020-12-15
CVE-2020-25187 Medtronic MyCareLink Smart Heap-based Buffer Overflow — Smart Model 25000 Patient Reader 8.8 High2020-12-14
CVE-2020-25199 Wecon Technologies LeviStudioU 缓冲区错误漏洞 — WECON Technology Co., Ltd LeviStudioU 7.8 -2020-12-09

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