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-2025-11779 Stack-based buffer overflow vulnreability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02
CVE-2025-20769 MediaTek Chipsets 安全漏洞 — MT2718, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793 6.7AIMediumAI2025-12-02
CVE-2025-12143 Stack Memory Corruption Vulnerability — Terra AC wallbox 6.1 Medium2025-11-28
CVE-2025-64344 Suricata is vulnerable to a stack overflow from unbounded stack allocation in LuaPushStringBuffer — suricata 7.5 High2025-11-26
CVE-2025-64331 Suricata is vulnerable to a stack overflow on large file transfers with http-body-printable — suricata 7.5 High2025-11-26
CVE-2025-64332 Suricata is vulnerable to a stack overflow on larger compressed data — suricata 7.5 High2025-11-26
CVE-2025-64333 Suricata is vulnerable to a stack overflow from big content-type — suricata 7.5 High2025-11-26
CVE-2025-59365 ASUS Router 安全漏洞 — Router 6.5AIMediumAI2025-11-25
CVE-2025-62691 Intercom MaLion Security Point 安全漏洞 — Security Point (Windows) of MaLion 9.8AICriticalAI2025-11-25
CVE-2025-52539 AMD Xilinx Run Time 安全漏洞 — Xilinx Run Time (XRT) 7.3 High2025-11-24
CVE-2025-40601 SonicWALL SonicOS SSLVPN 安全漏洞 — SonicOS 7.5 -2025-11-20
CVE-2025-13446 Tenda AC21 SetSysTimeCfg stack-based overflow — AC21 8.8 High2025-11-20
CVE-2025-13445 Tenda AC21 SetIpMacBind stack-based overflow — AC21 8.8 High2025-11-20
CVE-2025-53843 Fortinet FortiOS 安全漏洞 — FortiOS 6.9 High2025-11-18
CVE-2025-58413 Fortinet FortiOS 安全漏洞 — FortiOS 6.9 High2025-11-18
CVE-2025-8727 A stack buffer overflow vulnerability exists in the Supermicro BMC Web function(SSL). — X13SEDW-F 7.2 High2025-11-18
CVE-2025-8404 Stack buffer overflow vulnerability exists in the Supermicro BMC Shared library — MBD-X13SEDW-F 5.5 Medium2025-11-18
CVE-2025-8076 A stack buffer overflow vulnerability exists in the Supermicro BMC Web function — MBD-X13SEDW-F 7.2 High2025-11-18
CVE-2025-7623 Supermicro BMC SMASH services has a Stack-based buffer overflow vulnerability — MBD-X13SEDW-F 5.4 Medium2025-11-18
CVE-2025-13191 D-Link DIR-816L soap.cgi soapcgi_main stack-based overflow — DIR-816L 8.8 High2025-11-15
CVE-2025-13190 D-Link DIR-816L __ajax_exporer.sgi scandir_main stack-based overflow — DIR-816L 8.8 High2025-11-15
CVE-2025-13189 D-Link DIR-816L gena.cgi genacgi_main stack-based overflow — DIR-816L 8.8 High2025-11-15
CVE-2025-13188 D-Link DIR-816L authentication.cgi authenticationcgi_main stack-based overflow — DIR-816L 9.8 Critical2025-11-14
CVE-2025-11918 Rockwell Automation Arena® Simulation Stack-Based Buffer Overflow Vulnerability — Arena® Simulation 7.3 -2025-11-14
CVE-2025-7704 Supermicro BMC SMASH services has a Stack-based buffer overflow vulnerability — SYS-111C-NR 5.4 Medium2025-11-13
CVE-2021-4464 FIberHome AN5506-04-FA / HG6245D Routers Remote Stack Overflow — AN5506-04-FA 9.8 -2025-11-12
CVE-2025-33202 NVIDIA Triton Inference Server 安全漏洞 — Triton Inference Server 6.5 Medium2025-11-11
CVE-2024-47118 IBM Db2 is vulnerable to a denial of service as the server may crash under certain conditions with a specially crafted query — Db2 6.5 Medium2025-11-07
CVE-2025-54526 Fuji Electric Monitouch V-SFT-6 Stack-based Buffer Overflow — Monitouch V-SFT-6 7.8 High2025-11-04
CVE-2025-20749 MediaTek Chipsets 安全漏洞 — MT6789, MT6835, MT6855, MT6878, MT6879, MT6886, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8169, MT8188, MT8195, MT8196, MT8781, MT8796 6.7AIMediumAI2025-11-04

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