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-5043 Belkin F9K1122 Parameter formSetPassword stack-based overflow — F9K1122 8.8 High2026-03-29
CVE-2026-5042 Belkin F9K1122 Parameter formCrossBandSwitch stack-based overflow — F9K1122 8.8 High2026-03-29
CVE-2026-5037 mxml mxmlIndexNew mxml-index.c index_sort stack-based overflow — mxml 3.3 Low2026-03-29
CVE-2026-5036 Tenda 4G06 Endpoint DhcpListClient fromDhcpListClient stack-based overflow — 4G06 8.8 High2026-03-29
CVE-2026-5024 D-Link DIR-513 formSetEmail stack-based overflow — DIR-513 8.8 High2026-03-29
CVE-2026-5021 Tenda F453 httpd PPTPUserSetting fromPPTPUserSetting stack-based overflow — F453 8.8 High2026-03-29
CVE-2026-5004 Wavlink WL-WN579X3-C UPNP firewall.cgi sub_4019FC stack-based overflow — WL-WN579X3-C 8.8 High2026-03-28
CVE-2026-4975 Tenda AC15 POST Request setcfm formSetCfm memory corruption — AC15 8.8 High2026-03-27
CVE-2026-4974 Tenda AC7 POST Request SetSysTimeCfg fromSetSysTime memory corruption — AC7 8.8 High2026-03-27
CVE-2026-4961 Tenda AC6 POST Request QuickIndex formQuickIndex stack-based overflow — AC6 8.8 High2026-03-27
CVE-2026-4960 Tenda AC6 POST Request WizardHandle fromWizardHandle stack-based overflow — AC6 8.8 High2026-03-27
CVE-2023-7339 Data collection for dowloading leads into buffer overflow — pnGate 6.5 Medium2026-03-27
CVE-2026-4906 Tenda AC5 POST Request WizardHandle decodePwd stack-based overflow — AC5 8.8 High2026-03-27
CVE-2026-4905 Tenda AC5 POST Request WifiWpsOOB formWifiWpsOOB stack-based overflow — AC5 8.8 High2026-03-26
CVE-2026-4904 Tenda AC5 POST Request setcfm formSetCfm stack-based overflow — AC5 8.8 High2026-03-26
CVE-2026-4903 Tenda AC5 POST Request QuickIndex formQuickIndex memory corruption — AC5 8.8 High2026-03-26
CVE-2026-4902 Tenda AC5 POST Request addressNat fromAddressNat memory corruption — AC5 8.8 High2026-03-26
CVE-2026-33491 Zen-C has Stack-Based Buffer Overflow in Identifier Mangling — zenc 7.8 High2026-03-26
CVE-2026-23995 EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ — everest-core 8.4 High2026-03-26
CVE-2026-22790 EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload — everest-core 8.8 High2026-03-26
CVE-2026-4861 Wavlink WL-NU516U1 nas.cgi ftext stack-based overflow — WL-NU516U1 8.8 High2026-03-26
CVE-2026-4747 Remote code execution via RPCSEC_GSS packet validation — FreeBSD 8.8 -2026-03-26
CVE-2026-33307 mod_gnutils has stack-based buffer overflow caused by a long client certificate chain — mod_gnutls 7.5 High2026-03-24
CVE-2026-4567 Tenda A15 UploadCfg stack-based overflow — A15 9.8 Critical2026-03-23
CVE-2026-4566 Belkin F9K1122 formWISP5G stack-based overflow — F9K1122 8.8 High2026-03-23
CVE-2026-4555 D-Link DIR-513 boa formEasySetTimezone memory corruption — DIR-513 8.8 High2026-03-22
CVE-2026-4553 Tenda F453 Parameters Natlimit fromNatlimit stack-based overflow — F453 8.8 High2026-03-22
CVE-2026-4552 Tenda F453 Parameters VirtualSer fromVirtualSer memory corruption — F453 8.8 High2026-03-22
CVE-2026-4551 Tenda F453 Parameters SafeClientFilter fromSafeClientFilter memory corruption — F453 8.8 High2026-03-22
CVE-2026-4535 Tenda FH451 WrlclientSet stack-based overflow — FH451 8.8 High2026-03-22

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