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-36065 Adobe Photoshop Heap-Based Buffer Overflow Could Lead To Arbitrary Code Execution — Photoshop 7.8 High2021-09-01
CVE-2021-36056 XMP Toolkit SDK Heap-based Buffer Overflow Could Lead To Arbitrary Code Execution — XMP Toolkit 5.5 Medium2021-09-01
CVE-2021-36054 XMP Toolkit SDK Heap-based Buffer Overflow in the PSD_MetaHandler::CacheFileData Could Lead To Application Denial Of Service — XMP Toolkit 3.3 Low2021-09-01
CVE-2021-36050 XMP Toolkit SDK Heap-based Buffer Overflow Could Lead To Arbitrary Code Execution — XMP Toolkit 7.8 -2021-09-01
CVE-2021-33007 Delta Electronics TPEditor 安全漏洞 — Delta Electronics TPEditor 7.8 -2021-08-30
CVE-2021-28629 Adobe Animate heap corruption vulnerability could lead to arbitrary code execution — Animate 7.8 -2021-08-24
CVE-2021-28620 Adobe Animate heap corruption vulnerability could lead to arbitrary code execution — Animate 7.8 -2021-08-24
CVE-2021-28608 Adobe After Effects heap corruption vulnerability could lead to arbitrary code execution — After Effects 7.8 -2021-08-24
CVE-2021-28610 Adobe After Effects heap corruption vulnerability could lead to arbitrary code execution — After Effects 7.8 High2021-08-24
CVE-2021-28603 Adobe After Effects heap corruption vulnerability could lead to arbitrary code execution — After Effects 7.8 -2021-08-24
CVE-2021-28604 Adobe After Effects heap corruption vulnerability could lead to arbitrary code execution — After Effects 7.8 -2021-08-24
CVE-2021-28638 Adobe Acrobat Reader DC PDF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — Acrobat Reader 7.8 High2021-08-20
CVE-2021-28624 Adobe Bridge SGI File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability — Bridge 7.8 High2021-08-20
CVE-2021-21825 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T 9.8 -2021-08-18
CVE-2021-21810 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T Labs 9.8 -2021-08-17
CVE-2021-21829 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T 9.8 -2021-08-13
CVE-2021-21830 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T 9.8 -2021-08-13
CVE-2021-24036 Facebook HHVM 输入验证错误漏洞 — folly 9.8 -2021-07-23
CVE-2021-34329 Siemens JT2GO和Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2021-34328 Siemens JT2GO 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2021-34327 Siemens JT2GO 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2021-34326 Siemens Jt2go 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2021-34317 Siemens JT2GO 和 Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2021-34313 Siemens Jt2go 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2021-34312 Siemens JT2GO 和 Siemens Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 -2021-07-13
CVE-2020-28598 PrusaSlicer 缓冲区错误漏洞 — Prusa Research 7.8 -2021-07-08
CVE-2021-33000 Advantech WebAccess HMI Designer 缓冲区错误漏洞 — WebAccess HMI Designer 7.8 -2021-06-24
CVE-2021-21572 Dell BIOSConnect feature 缓冲区错误漏洞 — BIOSConnect 7.2 High2021-06-24
CVE-2021-31485 OpenText Brava! 缓冲区错误漏洞 — Brava! Desktop 7.8 -2021-06-15
CVE-2021-31483 OpenText Brava! 安全漏洞 — Brava! Desktop 7.8 -2021-06-15

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