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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

2750 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-11499 Tenda HG7HG9/HG10 formDOMAINBLK stack-based overflow — HG7HG9 9.8 Critical2026-06-08
CVE-2026-11498 Tenda HG7HG9/HG10 Web Management voip_other_set asp_voip_OtherSet stack-based overflow — HG7HG9 8.8 High2026-06-08
CVE-2026-11413 JingDong JD Cloud Box AX6600 jdcweb_rpc set_macfilter stack-based overflow — JD Cloud Box AX6600 8.8 High2026-06-06
CVE-2026-6240 Authenticated Stack-based Buffer Overflow in ONVIF DeleteUsers Service on TP-Link Tapo C520WS — Tapo C520WS v2--2026-06-05
CVE-2026-6239 Authenticated Stack-based Buffer Overflow in ONVIF CreateUsers Service in TP-Link Tao C520WS — Tapo C520WS v2--2026-06-05
CVE-2026-50259 Xorg-x11-server: xorg-x11-server-xwayland: xorg-x11-server: stack buffer overflow in xkb setmap request via mapwidths indexing — Red Hat Enterprise Linux 10 7.8 High2026-06-05
CVE-2026-50258 Xorg-x11-server: xorg-x11-server-xwayland: xorg-x11-server: stack buffer overflow in xkb key types due to unchecked shift levels — Red Hat Enterprise Linux 10 7.8 High2026-06-05
CVE-2026-50256 Xorg-x11-server: xorg-x11-server-xwayland: xorg-x11-server: stack buffer overflow in font alias resolution due to libxfont2 name length mismatch — Red Hat Enterprise Linux 10 7.8 High2026-06-05
CVE-2026-11024 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-10898 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-47318 SAMSUNG rLottie 安全漏洞 — rlottie 6.1 Medium2026-06-04
CVE-2026-35085 Stack buffer overflow in method gdv-serverconfig — Single-A 8.8 High2026-06-03
CVE-2026-35084 Stack buffer overflow in method dali-devconfig — Single-A 8.8 High2026-06-03
CVE-2026-35083 Stack buffer overflow in method bac-deviceobject — Single-A 8.8 High2026-06-03
CVE-2026-50031 FreeIPMI 安全漏洞 — FreeIPMI 7.5 High2026-06-03
CVE-2026-49943 BIRD 安全漏洞 — BIRD 6.3 Medium2026-06-02
CVE-2026-1871 Authenticated Stack-based Buffer Overflow in RTSP Authentication of Tapo C200 — Tapo C200 v5--2026-06-02
CVE-2026-10528 Orthanc DICOM Server DCMTK FromDcmtkBridge.cpp read stack-based overflow — DICOM Server 3.3 Low2026-06-02
CVE-2026-24085 Stack-based Buffer Overflow in Display — Snapdragon 7.2 High2026-06-01
CVE-2025-59613 Stack-based Buffer Overflow in Windows Compute — Snapdragon 6.7 Medium2026-06-01
CVE-2025-59612 Stack-based Buffer Overflow in Windows Compute — Snapdragon 6.7 Medium2026-06-01
CVE-2026-10293 UTT HiPER 1200GW formFireWall strcpy stack-based overflow — HiPER 1200GW 8.8 High2026-06-01
CVE-2018-25427 Arm Whois 3.11 Buffer Overflow via SEH Overwrite — Arm Whois 9.8 Critical2026-06-01
CVE-2026-10292 UTT HiPER 1200GW formTaskEdit strcpy stack-based overflow — HiPER 1200GW 8.8 High2026-06-01
CVE-2026-43623 microtar 0.1.0 Stack-Based Buffer Overflow via raw_to_header() — microtar 8.8 High2026-06-01
CVE-2026-43958 Rrdtool: rrdtool: stack buffer overflow allows local code execution or denial of service — Red Hat Enterprise Linux 10 7.8 High2026-06-01
CVE-2026-10270 D-Link DI-7001 MINI API httpd_debug.asp sprintf stack-based overflow — DI-7001 MINI 8.8 High2026-06-01
CVE-2026-0826 Poly Voice – Possible Remote Control of Certain Poly Devices — poly_trio_8300--2026-06-01
CVE-2026-10259 H3C Magic B0 aspForm SetMobileAPInfoById stack-based overflow — Magic B0 8.8 High2026-06-01
CVE-2026-10206 D-Link DI-8400 dbsrv.asp stack-based overflow — DI-8400 8.8 High2026-06-01

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