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-7421 Tenda O3V2 httpd operateMacFilter fromMacFilterModify stack-based overflow — O3V2 8.8 High2025-07-11
CVE-2025-7420 Tenda O3V2 httpd setWrlBasicInfo formWifiBasicSet stack-based overflow — O3V2 8.8 High2025-07-10
CVE-2025-7419 Tenda O3V2 httpd setRateTest fromSpeedTestSet stack-based overflow — O3V2 8.8 High2025-07-10
CVE-2025-7418 Tenda O3V2 httpd setPing fromPingResultGet stack-based overflow — O3V2 8.8 High2025-07-10
CVE-2025-7417 Tenda O3V2 httpd setPingInfo fromNetToolGet stack-based overflow — O3V2 8.8 High2025-07-10
CVE-2025-7416 Tenda O3V2 httpd setSysTimeInfo fromSysToolTime stack-based overflow — O3V2 8.8 High2025-07-10
CVE-2025-7206 D-Link DIR-825 httpd switch_language.cgi sub_410DDC stack-based overflow — DIR-825 9.8 Critical2025-07-08
CVE-2024-56468 IBM InfoSphere Data Replication VSAM for z/OS Remote Source denial of service — InfoSphere Data Replication VSAM for z/OS Remote Source 7.5 High2025-07-08
CVE-2025-47120 Adobe Framemaker | Stack-based Buffer Overflow (CWE-121) — Adobe Framemaker 5.5 Medium2025-07-08
CVE-2025-49528 Illustrator | Stack-based Buffer Overflow (CWE-121) — Illustrator 7.8 High2025-07-08
CVE-2025-49527 Illustrator | Stack-based Buffer Overflow (CWE-121) — Illustrator 7.8 High2025-07-08
CVE-2025-7194 D-Link DI-500WF jhttpd ip_position.asp sprintf stack-based overflow — DI-500WF 8.8 High2025-07-08
CVE-2025-5451 Ivanti Connect Secure 安全漏洞 — Connect Secure 4.9 Medium2025-07-08
CVE-2025-40741 Siemens Solid Edge SE2025 安全漏洞 — Solid Edge SE2025 7.8 High2025-07-08
CVE-2025-6663 GStreamer H266 Codec Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — GStreamer 9.8 -2025-07-07
CVE-2025-53176 Huawei HarmonyOS 安全漏洞 — HarmonyOS 3.3 Low2025-07-07
CVE-2025-53175 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-07-07
CVE-2025-53174 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-07-07
CVE-2025-53173 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.3 Medium2025-07-07
CVE-2025-53172 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-07-07
CVE-2025-53171 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-07-07
CVE-2024-58117 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.0 Medium2025-07-07
CVE-2025-7094 Belkin F9K1122 webs formBSSetSitesurvey stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7093 Belkin F9K1122 webs formSetLanguage stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7092 Belkin F9K1122 webs formWlanSetupWPS stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7091 Belkin F9K1122 webs formWlanMP stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7090 Belkin F9K1122 webs formConnectionSetting stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7089 Belkin F9K1122 webs formWanTcpipSetup stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7088 Belkin F9K1122 webs formPPPoESetup stack-based overflow — F9K1122 8.8 High2025-07-06
CVE-2025-7087 Belkin F9K1122 webs formL2TPSetup stack-based overflow — F9K1122 8.8 High2025-07-06

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