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-6122 Tenda F451 httpd L7Prot frmL7ProtForm stack-based overflow — F451 8.8 High2026-04-12
CVE-2026-6121 Tenda F451 httpd WrlclientSet stack-based overflow — F451 8.8 High2026-04-12
CVE-2026-6120 Tenda F451 httpd DhcpListClient fromDhcpListClient stack-based overflow — F451 8.8 High2026-04-12
CVE-2026-4156 ChargePoint Home Flex OCPP getpreq Stack-based Buffer Overflow Remote Code Execution Vulnerability — Home Flex 8.8AIHighAI2026-04-11
CVE-2026-5525 Stack-Based Buffer Overflow in Notepad++ File Drop Handler leads to DoS — Notepad++ 6.0 Medium2026-04-10
CVE-2026-6016 Tenda AC9 POST Request WizardHandle decodePwd stack-based overflow — AC9 8.8 High2026-04-10
CVE-2026-6015 Tenda AC9 POST Request QuickIndex formQuickIndex stack-based overflow — AC9 8.8 High2026-04-10
CVE-2026-5992 Tenda F451 P2pListFilter fromP2pListFilter stack-based overflow — F451 8.8 High2026-04-10
CVE-2026-5991 Tenda F451 WrlExtraSet formWrlExtraSet stack-based overflow — F451 8.8 High2026-04-09
CVE-2026-5990 Tenda F451 SafeEmailFilter fromSafeEmailFilter stack-based overflow — F451 8.8 High2026-04-09
CVE-2026-5989 Tenda F451 RouteStatic fromRouteStatic stack-based overflow — F451 8.8 High2026-04-09
CVE-2026-5988 Tenda F451 AdvSetWrlsafeset formWrlsafeset stack-based overflow — F451 8.8 High2026-04-09
CVE-2026-5295 Stack Buffer Overflow in wolfSSL PKCS7 wc_PKCS7_DecryptOri() via Oversized OID — wolfSSL 9.8AICriticalAI2026-04-09
CVE-2026-39853 osslsigncode has a Stack Buffer Overflow via Unbounded Digest Copy During Signature Verification — osslsigncode 7.8 High2026-04-09
CVE-2026-5830 Tenda AC15 SysToolChangePwd websGetVar stack-based overflow — AC15 8.8 High2026-04-09
CVE-2026-5815 D-Link DIR-645 hedwig.cgi hedwigcgi_main stack-based overflow — DIR-645 8.8 High2026-04-08
CVE-2026-30814 Buffer Overflow Vulnerability in TP-Link AX53 — AX53 v1.0 8.0AIHighAI2026-04-08
CVE-2026-5726 ASDA-Soft Stack-based Buffer Overflow Vulnerability — ASDA-Soft 7.8 High2026-04-08
CVE-2026-5687 Tenda CX12L NatStaticSetting fromNatStaticSetting stack-based overflow — CX12L 8.8 High2026-04-06
CVE-2026-5686 Tenda CX12L RouteStatic fromRouteStatic stack-based overflow — CX12L 8.8 High2026-04-06
CVE-2026-5685 Tenda CX12L addressNat fromAddressNat stack-based overflow — CX12L 8.8 High2026-04-06
CVE-2026-5684 Tenda CX12L webExcptypemanFilter fromwebExcptypemanFilter stack-based overflow — CX12L 8.0 High2026-04-06
CVE-2026-5683 Tenda CX12L P2pListFilter fromP2pListFilter stack-based overflow — CX12L 5.5 Medium2026-04-06
CVE-2025-47391 Stack-based Buffer Overflow in Camera Driver — Snapdragon 7.8 High2026-04-06
CVE-2026-5629 Belkin F9K1015 formSetFirewall stack-based overflow — F9K1015 8.8 High2026-04-06
CVE-2026-5628 Belkin F9K1015 Setting formSetSystemSettings stack-based overflow — F9K1015 8.8 High2026-04-06
CVE-2026-5614 Belkin F9K1015 formSetPassword stack-based overflow — F9K1015 8.8 High2026-04-06
CVE-2026-5613 Belkin F9K1015 formReboot stack-based overflow — F9K1015 8.8 High2026-04-06
CVE-2026-5612 Belkin F9K1015 formWlEncrypt stack-based overflow — F9K1015 8.8 High2026-04-06
CVE-2026-5611 Belkin F9K1015 formCrossBandSwitch stack-based overflow — F9K1015 8.8 High2026-04-06

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