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-2025-20747 MediaTek Chipsets 安全漏洞 — MT2718, MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6982, MT6985, MT6986, MT6986D, MT6989, MT6990, MT6991, MT8676, MT8678, MT8755, MT8893 6.7AIMediumAI2025-11-04
CVE-2025-20746 MediaTek Chipsets 安全漏洞 — MT2718, MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6982, MT6985, MT6986, MT6986D, MT6989, MT6990, MT6991, MT8676, MT8678, MT8755, MT8893 6.7AIMediumAI2025-11-04
CVE-2025-20739 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-11-04
CVE-2025-20738 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-11-04
CVE-2025-20736 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-11-04
CVE-2025-20732 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 6.7AIMediumAI2025-11-04
CVE-2025-20737 MediaTek Chipsets 安全漏洞 — MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 7.8AIHighAI2025-11-04
CVE-2025-47360 Stack-based Buffer Overflow in Automotive Software platform based on QNX — Snapdragon 7.8 High2025-11-04
CVE-2025-12464 Qemu-kvm: stack buffer overflow in e1000 device via short frames in loopback mode 6.2 Medium2025-10-31
CVE-2025-64096 CryptoLib vulnerable to Stack Buffer Overflow in Crypto_Key_Update due to missing TLV length check — CryptoLib 9.8AICriticalAI2025-10-30
CVE-2025-10925 GIMP ILBM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — GIMP 7.8AIHighAI2025-10-29
CVE-2025-40843 Buffer overflow in CodeChecker log command — CodeChecker 5.9 Medium2025-10-28
CVE-2025-12260 TOTOLINK A3300R POST Parameter cstecgi.cgi setSyslogCfg stack-based overflow — A3300R 8.8 High2025-10-27
CVE-2025-12259 TOTOLINK A3300R POST Parameter cstecgi.cgi setScheduleCfg stack-based overflow — A3300R 8.8 High2025-10-27
CVE-2025-12258 TOTOLINK A3300R POST Parameter cstecgi.cg setOpModeCfg stack-based overflow — A3300R 8.8 High2025-10-27
CVE-2025-12241 TOTOLINK A3300R POST Parameter cstecgi.cgi setLanguageCfg stack-based overflow — A3300R 8.8 High2025-10-27
CVE-2025-12225 Tenda AC6 HTTP Request WifiGuestSet stack-based overflow — AC6 8.8 High2025-10-27
CVE-2025-12214 Tenda O3 sysAutoReboot GetValue stack-based overflow — O3 8.8 High2025-10-27
CVE-2025-12213 Tenda O3 setVlanConfig GetValue stack-based overflow — O3 8.8 High2025-10-27
CVE-2025-12212 Tenda O3 setNetworkService GetValue stack-based overflow — O3 8.8 High2025-10-27
CVE-2025-12211 Tenda O3 setDmzInfo GetValue stack-based overflow — O3 8.8 High2025-10-27
CVE-2025-12210 Tenda O3 AdvSetLanip GetValue stack-based overflow — O3 8.8 High2025-10-27
CVE-2025-12209 Tenda O3 setDhcpConfig GetValue stack-based overflow — O3 8.8 High2025-10-27
CVE-2020-36855 DCMTK dcmqrscp parseQuota stack-based overflow — DCMTK 5.3 Medium2025-10-21
CVE-2025-11678 Stack-based Buffer Overflow in libwebsockets DNS response parsing — libwebsocket 9.8AICriticalAI2025-10-20
CVE-2025-5555 Nixdorf Wincor PORT IO Driver IOCTL wnport.sys sub_11100 stack-based overflow — PORT IO Driver 7.8 High2025-10-18
CVE-2025-62580 ASDA-Soft Stack-based Buffer Overflow Vulnerability — ASDA-Soft 7.8 High2025-10-16
CVE-2025-62579 ASDA-Soft Stack-based Buffer Overflow Vulnerability — ASDA-Soft 7.8 High2025-10-16
CVE-2025-20350 Cisco Desk Phone 9800 Series, IP Phone 7800 and 8800 Series, and Video Phone 8875 with SIP Firmware Denial of Service Vulnerability — Cisco Session Initiation Protocol (SIP) Software 7.5 High2025-10-15
CVE-2025-53521 BigIP APM Vulnerability — BIG-IP 9.8 Critical2025-10-15

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