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-34451 rofl0r/proxychains-ng <= 4.17 Stack-based Buffer Overflow — proxychains-ng 9.1AICriticalAI2025-12-18
CVE-2025-34450 merbanan/rtl_433 <= 25.02 Stack-based Buffer Overflow — rtl_433 8.8AIHighAI2025-12-18
CVE-2025-14879 Tenda WH450 HTTP Request onSSIDChange stack-based overflow — WH450 9.8 Critical2025-12-18
CVE-2025-14878 Tenda WH450 HTTP Request wirelessRestart stack-based overflow — WH450 9.8 Critical2025-12-18
CVE-2025-64469 Stack-based Buffer Overflow in LVResource::DetachResource() in NI LabVIEW — LabVIEW 7.8 High2025-12-18
CVE-2025-66635 SEIKO EPSON Web Config 安全漏洞 — Web Config 8.8AIHighAI2025-12-16
CVE-2023-53879 NVClient 5.0 Stack Buffer Overflow Vulnerability via User Configuration — NVClient 7.5AIHighAI2025-12-15
CVE-2023-53886 Xlight FTP Server 3.9.3.6 Stack Buffer Overflow Vulnerability via Execute Program — Xlight FTP Server 7.5AIHighAI2025-12-15
CVE-2025-14665 Tenda WH450 HTTP Request DhcpListClient stack-based overflow — WH450 9.8 Critical2025-12-14
CVE-2025-14655 Tenda AC20 httpd SetSysAutoRebbotCfg formSetRebootTimer stack-based overflow — AC20 8.8 High2025-12-14
CVE-2025-14654 Tenda AC20 httpd setPptpUserList formSetPPTPUserList stack-based overflow — AC20 8.8 High2025-12-14
CVE-2024-58299 PCMan FTP Server 2.0 Remote Buffer Overflow via 'pwd' Command — FTP Server 9.8 Critical2025-12-12
CVE-2025-66046 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-12-11
CVE-2025-66047 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-12-11
CVE-2025-66045 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-12-11
CVE-2025-66044 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-12-11
CVE-2025-66048 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-12-11
CVE-2025-66043 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-12-11
CVE-2025-41732 Stack-based buffer overflow via unsafe sscanf in check_cookie() — Indsutrial-Managed-Switches 9.8 Critical2025-12-10
CVE-2025-41730 Stack-based buffer overflow via unsafe sscanf in check_account() — Indsutrial-Managed-Switches 9.8 Critical2025-12-10
CVE-2025-14136 Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 mod_form.so stack-based overflow — RE6500 8.8 High2025-12-06
CVE-2025-14135 Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 mod_form.so AP_get_wired_clientlist_setClientsName stack-based overflow — RE6500 8.8 High2025-12-06
CVE-2025-14134 Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 mod_form.so stack-based overflow — RE6500 8.8 High2025-12-06
CVE-2025-14133 Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 mod_form.so AP_get_wireless_clientlist_setClientsName stack-based overflow — RE6500 8.8 High2025-12-06
CVE-2025-1547 WatchGuard Firebox Authenticated Stack Overflow in Certificate Request Command — Fireware OS 6.7AIMediumAI2025-12-04
CVE-2025-11786 Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02
CVE-2025-11785 Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02
CVE-2025-11784 Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02
CVE-2025-11783 Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02
CVE-2025-11782 Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02

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