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-4534 Tenda FH451 WrlExtraSet formWrlExtraSet stack-based overflow — FH451 8.8 High2026-03-22
CVE-2026-4529 D-Link DHP-1320 SOAP redirect_count_down_page stack-based overflow — DHP-1320 8.8 High2026-03-21
CVE-2026-33147 GMT: Stack-based Buffer Overflow in gmt_remote_dataset_id — gmt 7.3 High2026-03-20
CVE-2026-4493 Tenda A18 Pro MAC Filtering Configuration Endpoint setMacFilterCfg sub_423B50 stack-based overflow — A18 Pro 8.8 High2026-03-20
CVE-2026-4492 Tenda A18 Pro formSetQosBand set_qosMib_list stack-based overflow — A18 Pro 8.8 High2026-03-20
CVE-2026-4491 Tenda A18 Pro SetIpMacBind fromSetIpMacBind stack-based overflow — A18 Pro 8.8 High2026-03-20
CVE-2026-4490 Tenda A18 Pro openSchedWifi setSchedWifi stack-based overflow — A18 Pro 8.8 High2026-03-20
CVE-2025-15608 Buffer Overflow in Network Probe Handling Function of TP-Link Archer AX53 — AX53 v1 9.8 -2026-03-20
CVE-2025-59383 Media Streaming Add-on — Media Streaming Add-on 9.1 -2026-03-20
CVE-2026-4489 Tenda A18 Pro fast_setting_wifi_set form_fast_setting_wifi_set stack-based overflow — A18 Pro 8.8 High2026-03-20
CVE-2026-4486 D-Link DIR-513 Web Service formEasySetPassword stack-based overflow — DIR-513 8.8 High2026-03-20
CVE-2026-4444 Google Chrome 安全漏洞 — Chrome 8.8 -2026-03-20
CVE-2026-30872 OpenWrt Project has a Stack-based Buffer Overflow vulnerability via IPv6 reverse DNS lookup — openwrt 10.0 -2026-03-19
CVE-2026-30871 OpenWrt Project has Stack-based Buffer Overflow in DNS PTR Query — openwrt 10.0 -2026-03-19
CVE-2026-0819 Stack buffer overflow in PKCS7 SignedData encoding with custom signed attributes — wolfSSL 9.8 -2026-03-19
CVE-2025-69720 ncurses 安全漏洞 — ncurses 7.3 High2026-03-19
CVE-2026-32743 PX4 Autopilot: Stack-based Buffer Overflow via Oversized Path Input in MAVLink Log Request Handling — PX4-Autopilot 6.5 Medium2026-03-18
CVE-2026-31971 HTSlib CRAM decoder vulnerable to buffer overflow — htslib 9.8 -2026-03-18
CVE-2026-31968 HTSlib CRAM decoder vulnerable to buffer overflow — htslib 8.2 -2026-03-18
CVE-2026-22321 Stack-Based Buffer Overflow in CLI Login Username Handling over CLI — FL SWITCH 2005 5.3 Medium2026-03-18
CVE-2026-22320 Stack-Based Buffer Overflow in TFTP File-Transfer Command Handling over CLI — FL SWITCH 2005 6.5 Medium2026-03-18
CVE-2026-22319 Stack-Based Buffer Overflow in File Install Parameter Handling — FL SWITCH 2005 4.9 Medium2026-03-18
CVE-2026-22318 Stack-Based Buffer Overflow in File Transfer Parameter Handling — FL SWITCH 2005 4.9 Medium2026-03-18
CVE-2026-22316 Buffer Overflow using TFTP Filename — FL SWITCH 2005 6.5 Medium2026-03-18
CVE-2026-25790 Wazuh has Stack-Based Buffer Overflow in Security Configuration Assessment JSON Parser — wazuh 4.9 Medium2026-03-17
CVE-2026-25772 Wazuh Database Synchronization Vulnerable to Stack-based Buffer Overflow via snprintf Integer Underflow — wazuh 4.9 Medium2026-03-17
CVE-2026-4254 Tenda AC8 HTTP Endpoint SysToolChangePwd doSystemCmd stack-based overflow — AC8 9.8 Critical2026-03-16
CVE-2026-4226 LB-LINK BL-WR9000 get_virtual_cfg sub_44E8D0 stack-based overflow — BL-WR9000 8.8 High2026-03-16
CVE-2026-4214 D-Link DNS-1550-04 app_mgr.cgi UPnP_AV_Server_Path_Setting stack-based overflow — DNS-120 8.8 High2026-03-16
CVE-2026-4213 D-Link DNS-1550-04 gui_mgr.cgi cgi_myfavorite_verify stack-based overflow — DNS-120 8.8 High2026-03-16

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