Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-121 (栈缓冲区溢出) — Vulnerability Class 3224

3224 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)
Availability Modify 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 Control Modify 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, Other Modify 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 Compilation Use 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 Design Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation Implement and perform bounds checking on input.
Implementation Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors.
Operation, Build and Compilation Run 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 ID Title CVSS Severity Published
CVE-2026-42025 TOTOLINK X2000R 堆栈缓冲区溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-42026 TOTOLINK X2000R 栈溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-9817 TOTOLINK X2000R V1.0.0 boa 栈溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-9869 TOTOLINK X2000R 1.0.0 堆栈缓冲区溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-10132 TOTOLINK X2000R 特定版本 formIpQos 栈缓冲区溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-10133 TOTOLINK X2000R V1.0.0-B20250421.1327 栈缓冲区溢出 — Totolink 9.1 Critical 2026-10-20
CVE-2026-10137 TOTOLINK X2000R 特定版本 formUpload 栈溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-10139 TOTOLINK X2000R Mcli 栈缓冲区溢出漏洞 — Totolink 9.1 Critical 2026-10-20
CVE-2026-17518 ASUS 路由器固件缓冲区溢出漏洞致拒绝服务 — Router 8.2 High 2026-10-20
CVE-2026-112373 H3C Magic NX15 usrlist sub_416874 stack-based overflow — Magic NX15 6.5 Medium 2026-10-19
CVE-2026-112257 Gimp: gimp: heap out-of-bounds read/write in psd thumbnail loader (load_resource_1033) — Red Hat Enterprise Linux 10 7.8 High 2026-10-19
CVE-2026-105810 Authenticated Local Stack Overflow in TP-Link Tapo C320WS — Tapo C320WS v2 8.5 High 2026-10-19
CVE-2026-12665 IBM MQ Buffer Overflow — MQ Operator 8.1 High 2026-10-19
CVE-2026-112281 libaribb24 through 1.0.3 Stack Buffer Overflow via decoder_handle_csi — aribb24 6.1 Medium 2026-10-19
CVE-2026-108984 GV-ASManager Web Server Buffer Overflow Vulnerability — GV-ASManager 7.5 High 2026-10-19
CVE-2026-112063 libstrophe through 0.14.0 Stack-Based Buffer Overflow via SCRAM Salt in SCRAM_Hi — libstrophe 5.9 Medium 2026-10-18
CVE-2026-112062 lwIP through 2.2.1 Stack Out-of-Bounds Write via mDNS Search Response Handler — lwIP 5.9 Medium 2026-10-18
CVE-2026-111711 Netcore NR256CN through 1.5.140116 Pre-Auth Stack Overflow via Boa user_ok() — NR256CN 9.8 Critical 2026-10-16
CVE-2026-108445 Microsoft Office Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 8.8 High 2026-10-15
CVE-2026-108440 Microsoft Office Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 8.8 High 2026-10-15
CVE-2026-108431 Microsoft Office Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 8.8 High 2026-10-15
CVE-2026-79840 HPE NonStop XABroker - Memory corruption vulnerability — HPE NonStop XABroker 7.3 High 2026-10-15
CVE-2026-79839 HPE NonStop ODBC/MX Server - Memory corruption vulnerability — HPE NonStop ODBC/MX Server 7.3 High 2026-10-15
CVE-2026-79838 HPE NonStop ODBC/MX Services - Memory corruption vulnerability — HPE NonStop ODBC/MX Services 7.3 High 2026-10-15
CVE-2026-79832 HPE NonStop SQL/MX Executor - Buffer overflow vulnerability — HPE NonStop SQL/MX Executor 7.6 High 2026-10-15
CVE-2026-79830 HPE NonStop Kernel Level Thread Model Lib - Stack buffer overflow vulnerability — HPE NonStop Kernel Level Thread Model Lib 6.6 Medium 2026-10-15
CVE-2026-79823 HPE NonStop EMS Distributor - Buffer Overflow vulnerability — HPE NonStop EMS Distributor 4.0 Medium 2026-10-15
CVE-2026-76663 HPE NonStop TELSERV - Memory corruption vulnerability — HPE NonStop TELSERV 7.5 High 2026-10-15
CVE-2026-76662 HPE NonStop TELSERV - Memory corruption vulnerability — HPE NonStop TELSERV 5.9 Medium 2026-10-15
CVE-2026-73799 HPE NonStop SNMP Trap Multiplexer - Memory Corruption vulnerability — HPE NonStop SNMP Trap Multiplexer 7.5 High 2026-10-15

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