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-2026-21903 Junos OS: Subscribing to telemetry sensors at scale causes all FPCs to crash — Junos OS 6.5 Medium2026-01-15
CVE-2023-54334 Explorer32++ 1.3.5.531 - Buffer overflow — Explorer32++ 9.8 Critical2026-01-13
CVE-2023-54330 Inbit Messenger 4.9.0 - Unauthenticated Remote SEH Overflow — Inbit Messenger 9.8 Critical2026-01-13
CVE-2023-54329 Inbit Messenger 4.9.0 - Unauthenticated Remote Command Execution (RCE) — Inbit Messenger 9.8 Critical2026-01-13
CVE-2026-21224 Azure Connected Machine Agent Elevation of Privilege Vulnerability — Azure Connected Machine Agent 7.8 High2026-01-13
CVE-2026-22214 RIOT OS <= 2026.01-devel-317 Stack-Based Buffer Overflow in ethos Serial Frame Parser — RIOT OS 9.1AICriticalAI2026-01-12
CVE-2026-22213 RIOT OS <= 2026.01-devel-317 Stack-Based Buffer Overflow in tapslip6 Utility — RIOT OS 9.8AICriticalAI2026-01-12
CVE-2026-22212 TinyOS <= 2.1.2 Stack-Based Buffer Overflow in mcp2200gpio — TinyOS 5.5AIMediumAI2026-01-12
CVE-2025-68622 Espressif ESP-IDF USB Host UVC Class Driver has a stack buffer overflow in UVC descriptor printing — esp-usb 6.8 Medium2026-01-12
CVE-2025-69195 Wget2: gnu wget2: memory corruption and crash via filename sanitization logic with attacker-controlled urls 7.6 High2026-01-09
CVE-2026-0719 Libsoup: signed to unsigned conversion error leading to stack-based buffer overflow in libsoup ntlm authentication — Red Hat Enterprise Linux 10 8.6 High2026-01-08
CVE-2026-22189 Panda3D <= 1.10.16 egg-mkfont Stack Buffer Overflow — Panda3D 9.8 -2026-01-07
CVE-2025-20797 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-20794 MediaTek chipsets 安全漏洞 — MediaTek chipset 7.5 -2026-01-06
CVE-2025-62852 QTS, QuTS hero — QTS 6.5 -2026-01-02
CVE-2025-53597 License Center — License Center 8.1 -2026-01-02
CVE-2025-53593 QTS, QuTS hero — QTS 6.5 -2026-01-02
CVE-2025-34468 libcoap Stack-Based Buffer Overflow in Address Resolution DoS or Potential RCE — libcoap 8.1 -2025-12-31
CVE-2025-15273 FontForge PFB File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — FontForge 7.8 -2025-12-31
CVE-2025-15255 Tenda W6-S R7websSsecurityHandler httpd stack-based overflow — W6-S 9.8 Critical2025-12-30
CVE-2025-15253 Tenda M3 exeCommand stack-based overflow — M3 8.8 High2025-12-30
CVE-2025-15252 Tenda M3 setDhcpAP formSetRemoteDhcpForAp stack-based overflow — M3 8.8 High2025-12-30
CVE-2025-15232 Tenda M3 setAdPushInfo formSetAdPushInfo stack-based overflow — M3 8.8 High2025-12-30
CVE-2025-15231 Tenda M3 setVlanInfo formSetRemoteVlanInfo stack-based overflow — M3 8.8 High2025-12-30
CVE-2025-15216 Tenda AC23 SetIpMacBind fromSetIpMacBind stack-based overflow — AC23 8.8 High2025-12-30
CVE-2025-15194 D-Link DIR-600 HTTP Header hedwig.cgi stack-based overflow — DIR-600 9.8 Critical2025-12-29
CVE-2025-15190 D-Link DWR-M920 formFilter sub_42261C stack-based overflow — DWR-M920 8.8 High2025-12-29
CVE-2025-15180 Tenda WH450 HTTP Request webExcptypemanFilte stack-based overflow — WH450 7.2 High2025-12-29
CVE-2025-15179 Tenda WH450 qossetting stack-based overflow — WH450 7.2 High2025-12-29
CVE-2025-15178 Tenda WH450 HTTP Request VirtualSer stack-based overflow — WH450 7.2 High2025-12-29

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