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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-121 (栈缓冲区溢出) — Vulnerability Class 2518

2518 vulnerabilities classified as CWE-121 (栈缓冲区溢出). AI Chinese analysis included.

CWE-121 represents a critical memory safety weakness where program data exceeds the allocated bounds of a stack-allocated buffer, corrupting adjacent memory structures. Attackers typically exploit this vulnerability by injecting malicious payloads that overwrite the function’s return address or saved frame pointer, thereby hijacking control flow to execute arbitrary code with the privileges of the compromised process. This exploitation is particularly dangerous because stack buffers are local variables, making the attack surface common in low-level languages like C and C++. Developers mitigate this risk by enforcing strict input validation, utilizing safe string handling functions that prevent unbounded writes, and adopting modern programming languages with automatic memory management. Additionally, implementing compiler-level protections such as stack canaries and Address Space Layout Randomization significantly raises the barrier for successful exploitation, ensuring system integrity remains intact against buffer overflow attempts.

MITRE CWE Description
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Common Consequences (3)
AvailabilityModify Memory, DoS: 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 ControlModify Memory, Execute Unauthorized Code or Commands, Bypass Protection Mechanism
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy.
Integrity, Confidentiality, Availability, Access Control, OtherModify Memory, Execute 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)
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
Architecture and DesignUse an abstraction library to abstract away risky APIs. Not a complete solution.
ImplementationImplement and perform bounds checking on input.
ImplementationDo not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors.
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
Examples (2)
While buffer overflow examples can be rather complex, it is possible to have very simple, yet still exploitable, stack-based buffer overflows:
#define BUFSIZE 256 int main(int argc, char **argv) { char buf[BUFSIZE]; strcpy(buf, argv[1]); }
Bad · C
This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.
void host_lookup(char *user_supplied_addr){ struct hostent *hp; in_addr_t *addr; char hostname[64]; in_addr_t inet_addr(const char *cp); /*routine that ensures user_supplied_addr is in the right format for conversion */ validate_addr_form(user_supplied_addr); addr = inet_addr(user_supplied_addr); hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET); strcpy(hostname, hp->h_name); }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2022-35690 Adobe ColdFusion ODBC Agent Stack-based Buffer Overflow Remote Code Execution Vulnerability — ColdFusion 9.8 Critical2022-10-14
CVE-2022-35710 Adobe ColdFusion ODBC Server Stack-based Buffer Overflow Remote Code Execution Vulnerability — ColdFusion 9.8 Critical2022-10-14
CVE-2022-38672 UNISOC chipset 缓冲区错误漏洞 — SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8000 5.5 -2022-10-14
CVE-2022-32493 Dell BIOS 缓冲区错误漏洞 — CPG BIOS 6.0 Medium2022-10-12
CVE-2022-35299 SAP SQL Anywhere 安全漏洞 — SAP SQL Anywhere 9.8 -2022-10-11
CVE-2022-36063 USBX Host CDC ECM integer underflow with buffer overflow — usbx 7.6 High2022-10-10
CVE-2022-40159 Stack Overflow in JXPath — jxpath 6.5 -2022-10-06
CVE-2022-40160 Stack Overflow in JXPath — jxpath 6.5 -2022-10-06
CVE-2022-23006 Buffer Overflow Vulnerability in Western Digital My Cloud Home Products and SanDisk ibi — My Cloud Home 1.8 Low2022-09-27
CVE-2022-3324 Stack-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-09-27
CVE-2022-3296 Stack-based Buffer Overflow in vim/vim — vim/vim 7.8 -2022-09-25
CVE-2022-2970 MZ Automation libIEC61850 Stack-Based Buffer Overflow — libIEC61850 10.0 Critical2022-09-23
CVE-2022-2972 MZ Automation libIEC61850 Stack-Based Buffer Overflow — libIEC61850 10.0 Critical2022-09-23
CVE-2022-2070 Grandstream GSD3710 Stack-based Buffer Overflow — Grandstream GSD3710 9.8 Critical2022-09-23
CVE-2022-2025 Grandstream GSD3710 Stack-based Buffer Overflow — Grandstream GSD3710 9.8 Critical2022-09-23
CVE-2022-40250 Stack overflow vulnerability in SMI handler on SmmSmbiosElog. — Aptio 8.2 -2022-09-20
CVE-2022-26873 The stack buffer overflow vulnerability in PlatformInitAdvancedPreMem leads to arbitrary code execution during PEI phase. — Aptio 8.2 -2022-09-20
CVE-2022-40152 Stack Buffer Overflow in Woodstox — Woodstox 6.5 Medium2022-09-16
CVE-2022-40151 Stack Buffer Overflow in xstream — xstream 6.5 Medium2022-09-16
CVE-2022-40149 Stack Buffer Overflow in Jettison — Jettison 6.5 Medium2022-09-16
CVE-2022-2471 Stack-Based Buffer Overflow Vulnerability in the EZVIZ Motion Detection component — CS-CV248 9.9 Critical2022-09-15
CVE-2022-31226 Dell BIOS 缓冲区错误漏洞 — CPG BIOS 7.1 High2022-09-12
CVE-2022-26860 Dell BIOS 缓冲区错误漏洞 — CPG BIOS 7.5 High2022-09-06
CVE-2022-25308 fribidi 缓冲区错误漏洞 — fribidi 7.8 -2022-09-06
CVE-2022-2402 Stack Overflow in ESET Endpoint Encryption and ESET Full Disk Encryption for Windows — ESET Endpoint Encryption 6.5 Medium2022-09-06
CVE-2022-38749 DoS in SnakeYAML — SnakeYAML 6.5 Medium2022-09-05
CVE-2022-38750 DoS in SnakeYAML — SnakeYAML 6.5 Medium2022-09-05
CVE-2022-38751 DoS in SnakeYAML — SnakeYAML 6.5 Medium2022-09-05
CVE-2022-38752 DoS in SnakeYAML — SnakeYAML 6.5 Medium2022-09-05
CVE-2022-2895 Measuresoft ScadaPro Server Stack-based Buffer Overflow — ScadaPro Server 7.8 High2022-08-31

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