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-3677 Tenda FH451 setcfm fromSetCfm stack-based overflow — FH451 8.8 High2026-03-07
CVE-2026-29068 PJSIP: Stack buffer overflow in Opus codec parser — pjproject 7.5 -2026-03-06
CVE-2026-3613 Wavlink WL-NU516U1 login.cgi sub_401A0C stack-based overflow — WL-NU516U1 7.2 High2026-03-06
CVE-2026-3439 SonicWALL SonicOS 安全漏洞 — SonicOS 7.5AIHighAI2026-03-04
CVE-2026-3400 Tenda AC15 TextEditingConversion stack-based overflow — AC15 8.8 High2026-03-01
CVE-2026-28422 Vim has stack-buffer-overflow in build_stl_str_hl() — vim 2.2 Low2026-02-27
CVE-2026-24497 SimTech ThinkWise 安全漏洞 — ThinkWise 9.8 -2026-02-27
CVE-2026-23747 Golioth Firmware SDK < 0.22.0 Payload Utils Stack-based Buffer Overflow — Firmware SDK 3.7 Low2026-02-26
CVE-2026-27821 GPAC NHML Demuxer (dmx_nhml.c) Vulnerable to Stack Buffer Overflow — gpac 8.1AIHighAI2026-02-26
CVE-2026-3137 CodeAstro Food Ordering System food_ordering.exe stack-based overflow — Food Ordering System 5.3 Medium2026-02-25
CVE-2026-0399 SonicWALL SonicOS 安全漏洞 — SonicOS 8.8AIHighAI2026-02-24
CVE-2026-25968 ImageMagick has MSL attribute stack buffer overflow that leads to out of bounds write. — ImageMagick 7.4 High2026-02-24
CVE-2026-25967 ImageMagick has stack buffer overflow in FTXT reader via oversized integer field — ImageMagick 7.4 High2026-02-24
CVE-2026-3044 Tenda AC8 Httpd Service UploadCfg webCgiGetUploadFile stack-based overflow — AC8 8.8 High2026-02-23
CVE-2026-2962 D-Link DWR-M960 Scheduled Reboot Configuration Endpoint formDateReboot sub_460F30 stack-based overflow — DWR-M960 8.8 High2026-02-23
CVE-2026-2961 D-Link DWR-M960 VPN Configuration Endpoint formVpnConfigSetup sub_4196C4 stack-based overflow — DWR-M960 8.8 High2026-02-23
CVE-2026-2960 D-Link DWR-M960 formDhcpv6s sub_468D64 stack-based overflow — DWR-M960 8.8 High2026-02-23
CVE-2026-2959 D-Link DWR-M960 formNewSchedule sub_44E0F8 stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2958 D-Link DWR-M960 formWsc sub_457C5C stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2930 Tenda A18 Httpd Service UploadCfg webCgiGetUploadFile stack-based overflow — A18 6.3 Medium2026-02-22
CVE-2026-2929 D-Link DWR-M960 Wireless Access Control Endpoint formWlAc sub_453140 stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2928 D-Link DWR-M960 WLAN Encryption Configuration Endpoint formWlEncrypt sub_452CCC stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2927 D-Link DWR-M960 Operation Mode Configuration Endpoint formOpMode sub_462590 stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2926 D-Link DWR-M960 LTE Configuration Endpoint formLteSetup sub_4237AC stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2925 D-Link DWR-M960 Bridge VLAN Configuration Endpoint formBridgeVlan sub_42B5A0 stack-based overflow — DWR-M960 8.8 High2026-02-22
CVE-2026-2910 Tenda HG9 formPing6 stack-based overflow — HG9 8.8 High2026-02-22
CVE-2026-2909 Tenda HG9 Diagnostic Ping Endpoint formPing stack-based overflow — HG9 8.8 High2026-02-22
CVE-2026-2908 Tenda HG9 Loopback Detection Configuration Endpoint formLoopBack stack-based overflow — HG9 8.8 High2026-02-22
CVE-2026-2907 Tenda HG9 GPON Configuration Endpoint formgponConf stack-based overflow — HG9 8.8 High2026-02-22
CVE-2026-2906 Tenda HG9 Samba Configuration Endpoint formSamba stack-based overflow — HG9 8.8 High2026-02-22

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