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-5610 Belkin F9K1015 formWISP5G stack-based overflow — F9K1015 8.8 High2026-04-06
CVE-2026-5609 Tenda i12 Parameter wifiSSIDset formwrlSSIDset stack-based overflow — i12 8.8 High2026-04-06
CVE-2026-5608 Belkin F9K1122 formWlanSetup stack-based overflow — F9K1122 8.8 High2026-04-06
CVE-2026-5605 Tenda CH22 WrlExtraSet formWrlExtraSet stack-based overflow — CH22 8.8 High2026-04-05
CVE-2026-5604 Tenda CH22 Parameter CertLocalPrecreate formCertLocalPrecreate stack-based overflow — CH22 8.8 High2026-04-05
CVE-2026-5550 Tenda AC10 httpd fromSysToolChangePwd stack-based overflow — AC10 8.8 High2026-04-05
CVE-2026-5548 Tenda AC10 httpd fromSysToolChangePwd stack-based overflow — AC10 8.8 High2026-04-05
CVE-2026-5544 UTT HiPER 1250GW formRemoteControl stack-based overflow — HiPER 1250GW 8.8 High2026-04-05
CVE-2026-34122 Stack-based Buffer Overflow Leading to Denial of Service in TP-Link Tapo C520WS — Tapo C520WS v2.6 7.5AIHighAI2026-04-02
CVE-2026-5350 Trendnet TEW-657BRM setup.cgi update_pcdb stack-based overflow — TEW-657BRM 8.8 High2026-04-02
CVE-2026-5349 Trendnet TEW-657BRM setup.cgi add_apcdb stack-based overflow — TEW-657BRM 8.8 High2026-04-02
CVE-2026-5245 Cesanta Mongoose mDNS Record mongoose.c handle_mdns_record stack-based overflow — Mongoose 5.6 Medium2026-04-02
CVE-2026-32928 Fuji Electric V-SFT 安全漏洞 — V-SFT 7.8 High2026-04-01
CVE-2026-32925 Fuji Electric V-SFT 安全漏洞 — V-SFT 7.8 High2026-04-01
CVE-2026-34555 iccDEV: SBO in CIccTagFixedNum::GetValues() — iccDEV 6.2 Medium2026-03-31
CVE-2026-34542 iccDEV: SBO in CIccCalculatorFunc::Apply() — iccDEV 6.2 Medium2026-03-31
CVE-2026-5214 D-Link DNS-1550-04 account_mgr.cgi cgi_addgroup_get_group_quota_minsize stack-based overflow — DNS-120 8.8 High2026-03-31
CVE-2026-5213 D-Link DNS-1550-04 account_mgr.cgi cgi_adduser_to_session stack-based overflow — DNS-120 8.8 High2026-03-31
CVE-2026-5212 D-Link DNS-1550-04 webdav_mgr.cgi Webdav_Upload_File stack-based overflow — DNS-120 8.8 High2026-03-31
CVE-2026-5211 D-Link DNS-1550-04 app_mgr.cgi UPnP_AV_Server_Path_Del stack-based overflow — DNS-120 8.8 High2026-03-31
CVE-2026-5204 Tenda CH22 Parameter webtypelibrary formWebTypeLibrary stack-based overflow — CH22 8.8 High2026-03-31
CVE-2026-5156 Tenda CH22 Parameter QuickIndex formQuickIndex stack-based overflow — CH22 8.8 High2026-03-30
CVE-2026-5155 Tenda CH22 Parameter AdvSetWan fromAdvSetWan stack-based overflow — CH22 8.8 High2026-03-30
CVE-2026-5154 Tenda CH22 Parameter setcfm fromSetCfm stack-based overflow — CH22 8.8 High2026-03-30
CVE-2026-5152 Tenda CH22 createFileName formCreateFileName stack-based overflow — CH22 8.8 High2026-03-30
CVE-2025-66215 OpenSC: Stack-buffer-overflow WRITE in card-oberthur — OpenSC 3.8 Low2026-03-30
CVE-2025-49010 OpenSC: Stack-buffer-overflow WRITE in GET RESPONSE — OpenSC 3.8 Low2026-03-30
CVE-2026-5046 Tenda FH1201 Parameter WrlExtraSet formWrlExtraSet stack-based overflow — FH1201 8.8 High2026-03-29
CVE-2026-5045 Tenda FH1201 Parameter WrlclientSet stack-based overflow — FH1201 8.8 High2026-03-29
CVE-2026-5044 Belkin F9K1122 Setting formSetSystemSettings stack-based overflow — F9K1122 8.8 High2026-03-29

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