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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2533 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-5228 D-Link DI-8100 jhttpd login.cgi httpd_get_parm stack-based overflow — DI-8100 8.8 High2025-05-27
CVE-2025-5215 D-Link DCS-5020L ptdc.cgi websReadEvent stack-based overflow — DCS-5020L 8.8 High2025-05-27
CVE-2025-5080 Tenda FH451 webExcptypemanFilter stack-based overflow — FH451 8.8 High2025-05-22
CVE-2025-3481 MedDream PACS Server DICOM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — PACS Server 9.8AICriticalAI2025-05-22
CVE-2025-3482 MedDream PACS Server DICOM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — PACS Server 9.8AICriticalAI2025-05-22
CVE-2025-3483 MedDream PACS Server DICOM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — PACS Server 9.8AICriticalAI2025-05-22
CVE-2025-3484 MedDream PACS Server DICOM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — PACS Server 9.8AICriticalAI2025-05-22
CVE-2025-3887 GStreamer H265 Codec Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability — GStreamer 9.8AICriticalAI2025-05-22
CVE-2025-41426 Vertiv Liebert RDU101 and UNITY Stack-based Buffer Overflow — Liebert RDU101 9.8 Critical2025-05-21
CVE-2025-48060 AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt) — jq 6.5AIMediumAI2025-05-21
CVE-2025-40634 Stack-based buffer overflow in TP-Link Archer AX50 — Link Archer AX50 9.8AICriticalAI2025-05-20
CVE-2025-47760 Fuji Electric V-SFT 安全漏洞 — V-SFT 7.8 High2025-05-19
CVE-2025-47759 Fuji Electric V-SFT 安全漏洞 — S-SFT 7.8 High2025-05-19
CVE-2025-47758 Fuji Electric V-SFT 安全漏洞 — V-SFT 7.8 High2025-05-19
CVE-2025-4892 code-projects Police Station Management System Delete Record source.cpp remove stack-based overflow — Police Station Management System 5.3 Medium2025-05-18
CVE-2025-4890 code-projects Tourism Management System Login User LoginUser stack-based overflow — Tourism Management System 5.3 Medium2025-05-18
CVE-2025-4883 D-Link DI-8100 Connection Limit Page ctxz.asp ctxz_asp stack-based overflow — DI-8100 7.2 High2025-05-18
CVE-2025-4843 D-Link DCS-932L udev SubUPnPCSInit stack-based overflow — DCS-932L 8.8 High2025-05-17
CVE-2025-4842 D-Link DCS-932L ucp isUCPCameraNameChanged stack-based overflow — DCS-932L 8.8 High2025-05-17
CVE-2025-4841 D-Link DCS-932L gpio sub_404780 stack-based overflow — DCS-932L 8.8 High2025-05-17
CVE-2025-4810 Tenda AC7 SetRebootTimer formSetRebootTimer stack-based overflow — AC7 8.8 High2025-05-16
CVE-2025-4809 Tenda AC7 setMacFilterCfg fromSafeSetMacFilter stack-based overflow — AC7 8.8 High2025-05-16
CVE-2025-30421 Stack-based Buffer Overflow in DrObjectStorage::XML_Serialize() in NI Circuit Design Suite — Circuit Design Suite 7.8 High2025-05-15
CVE-2025-29840 Windows Media Remote Code Execution Vulnerability — Windows 10 Version 1507 8.8 High2025-05-13
CVE-2025-32756 Fortinet多款产品 安全漏洞 — FortiNDR 9.6 Critical2025-05-13
CVE-2025-40580 Siemens SCALANCE LPE9403 安全漏洞 — SCALANCE LPE9403 6.7 Medium2025-05-13
CVE-2025-40579 Siemens SCALANCE LPE9403 安全漏洞 — SCALANCE LPE9403 6.7 Medium2025-05-13
CVE-2025-3916 Schneider Electric EcoStruxure Power Build Rapsody 安全漏洞 — EcoStruxure™ Power Build Rapsody software 7.8AIHighAI2025-05-13
CVE-2025-1533 ASUS Armoury Crate 安全漏洞 — Armoury Crate 7.8AIHighAI2025-05-12
CVE-2025-4544 D-Link DI-8100 jhttpd ddos.asp stack-based overflow — DI-8100 6.6 Medium2025-05-11

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