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-2017-20205 Valve Source SDK Stack-Based Buffer Overflow RCE — Source SDK (source-sdk-2013) 9.8AICriticalAI2025-10-15
CVE-2025-54274 Substance3D - Viewer | Stack-based Buffer Overflow (CWE-121) — Substance3D - Viewer 7.8 High2025-10-14
CVE-2025-24052 Windows Agere Modem Driver Elevation of Privilege Vulnerability — Windows 10 Version 1507 7.8 High2025-10-14
CVE-2023-46718 Fortinet FortiOS 安全漏洞 — FortiOS 6.3 Medium2025-10-14
CVE-2025-20717 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-10-14
CVE-2025-20714 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-10-14
CVE-2025-20713 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-10-14
CVE-2025-20719 MediaTek Chipsets 安全漏洞 — MT6890, MT7603, MT7615, MT7622, MT7915, MT7916, MT7981, MT7986 8.8AIHighAI2025-10-14
CVE-2025-20718 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 7.8AIHighAI2025-10-14
CVE-2025-9336 ASUS Armoury Crate 安全漏洞 — Armoury Crate 7.8AIHighAI2025-10-13
CVE-2025-58301 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.2 Medium2025-10-11
CVE-2025-58300 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.2 Medium2025-10-11
CVE-2025-58298 Huawei HarmonyOS 安全漏洞 — HarmonyOS 7.3 High2025-10-11
CVE-2025-58297 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.9 Medium2025-10-11
CVE-2025-58295 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.9 Medium2025-10-11
CVE-2025-11586 Tenda AC7 setNotUpgrade stack-based overflow — AC7 8.8 High2025-10-10
CVE-2025-61856 Fuji Electric V-SFT 安全漏洞 — V-SFT 7.8 High2025-10-10
CVE-2025-11549 Tenda W12 HTTP Request modules wifiMacFilterSet stack-based overflow — W12 8.8 High2025-10-09
CVE-2025-47347 Stack-based Buffer Overflow in Automotive Software platform based on QNX — Snapdragon 7.8 High2025-10-09
CVE-2025-11528 Tenda AC7 saveAutoQos stack-based overflow — AC7 8.8 High2025-10-09
CVE-2025-11527 Tenda AC7 fast_setting_pppoe_set stack-based overflow — AC7 8.8 High2025-10-09
CVE-2025-11526 Tenda AC7 WifiMacFilterSet stack-based overflow — AC7 8.8 High2025-10-09
CVE-2025-11525 Tenda AC7 SetUpnpCfg stack-based overflow — AC7 8.8 High2025-10-09
CVE-2025-11524 Tenda AC7 SetDDNSCfg stack-based overflow — AC7 8.8 High2025-10-09
CVE-2025-11418 Tenda CH22 HTTP Request AdvSetWrlsafeset formWrlsafeset stack-based overflow — CH22 9.8 Critical2025-10-08
CVE-2025-43910 Dell PowerProtect Data Domain 安全漏洞 — PowerProtect Data Domain with Data Domain Operating System (DD OS) of Feature Release 2.3 Low2025-10-07
CVE-2025-45375 Dell PowerProtect Data Domain 安全漏洞 — PowerProtect Data Domain with Data Domain Operating System (DD OS) of Feature Release 4.4 Medium2025-10-07
CVE-2025-54401 Planet WGR-500 安全漏洞 — WGR-500 8.8 High2025-10-07
CVE-2025-54402 Planet WGR-500 安全漏洞 — WGR-500 8.8 High2025-10-07
CVE-2025-54399 Planet WGR-500 安全漏洞 — WGR-500 8.8 High2025-10-07

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