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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2532 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-2025-3693 Tenda W12 httpd cgiWifiRadioSet stack-based overflow — W12 8.8 High2025-04-16
CVE-2025-3588 joelittlejohn jsonschema2pojo JSON File SchemaRule.java apply stack-based overflow — jsonschema2pojo 5.3 Medium2025-04-14
CVE-2025-3538 D-Link DI-8100 jhttpd auth.asp auth_asp stack-based overflow — DI-8100 8.8 High2025-04-13
CVE-2025-23388 Unauthenticated stack overflow in /v3-public/authproviders API — rancher 8.2 High2025-04-11
CVE-2025-32387 Helm Allows A Specially Crafted JSON Schema To Cause A Stack Overflow — helm 6.5 Medium2025-04-09
CVE-2025-29988 Dell Client Platform BIOS 安全漏洞 — Dell Client Platform BIOS 6.9 Medium2025-04-09
CVE-2025-30298 Adobe Framemaker | Stack-based Buffer Overflow (CWE-121) — Adobe Framemaker 7.8 High2025-04-08
CVE-2025-27481 Windows Telephony Service Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-04-08
CVE-2025-26688 Microsoft Virtual Hard Disk Elevation of Privilege Vulnerability — Windows 10 Version 1507 7.8 High2025-04-08
CVE-2025-3409 Nothings stb stb_include_string stack-based overflow — stb 6.3 Medium2025-04-08
CVE-2024-58116 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-04-07
CVE-2024-58115 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-04-07
CVE-2025-3266 qinguoyi TinyWebServer http_conn.cpp stack-based overflow — TinyWebServer 7.3 High2025-04-04
CVE-2025-3259 Tenda RX3 SetOnlineDevName formSetDeviceName stack-based overflow — RX3 8.8 High2025-04-04
CVE-2025-3203 Tenda W18E setModules formSetAccountList stack-based overflow — W18E 4.3 Medium2025-04-04
CVE-2025-3196 Open Asset Import Library Assimp Malformed File MD2Loader.cpp InternReadFile stack-based overflow — Assimp 5.3 Medium2025-04-04
CVE-2025-3166 code-projects Product Management System Search Product Menu search_item stack-based overflow — Product Management System 5.3 Medium2025-04-03
CVE-2025-22457 Ivanti Connect Secure 安全漏洞 — Connect Secure 9.0 Critical2025-04-03
CVE-2025-3161 Tenda AC10 ShutdownSetAdd stack-based overflow — AC10 8.8 High2025-04-03
CVE-2025-3007 Novastar CX40 NetFilter Utility netconfig getopt stack-based overflow — CX40 5.5 Medium2025-03-31
CVE-2025-2837 Silicon Labs Gecko OS HTTP Request Handling Stack-based Buffer Overflow Remote Code Execution Vulnerability — Gecko OS 8.8AIHighAI2025-03-26
CVE-2025-2621 D-Link DAP-1620 storage check_dws_cookie stack-based overflow — DAP-1620 9.8 Critical2025-03-22
CVE-2025-2620 D-Link DAP-1620 Authentication storage mod_graph_auth_uri_handler stack-based overflow — DAP-1620 9.8 Critical2025-03-22
CVE-2025-2619 D-Link DAP-1620 Cookie storage check_dws_cookie stack-based overflow — DAP-1620 9.8 Critical2025-03-22
CVE-2025-30472 Corosync 安全漏洞 — Corosync 9.0 Critical2025-03-22
CVE-2024-13903 quickjs-ng QuickJS qjs quickjs.c JS_GetRuntime stack-based overflow — QuickJS 4.3 Medium2025-03-21
CVE-2025-26336 Dell PowerEdge FX2和Dell PowerEdge VRTX 安全漏洞 — Dell Chassis Management Controller (CMC) for Dell PowerEdge FX2 8.3 High2025-03-21
CVE-2025-1758 Progress LoadMaster 安全漏洞 — LoadMaster 4.3 Medium2025-03-19
CVE-2025-2370 TOTOLINK EX1800T cstecgi.cgi setWiFiExtenderConfig stack-based overflow — EX1800T 8.8 High2025-03-17
CVE-2025-2369 TOTOLINK EX1800T cstecgi.cgi setPasswordCfg stack-based overflow — EX1800T 8.8 High2025-03-17

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