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-54488 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54483 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54490 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54485 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54487 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54481 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54482 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-54480 libbiosig 安全漏洞 — libbiosig 9.8 Critical2025-08-25
CVE-2025-46411 BioSig Project Biosig Project libbiosig和ch 安全漏洞 — libbiosig 8.1 High2025-08-25
CVE-2025-9393 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 addStaProfile stack-based overflow — RE6250 8.8 High2025-08-24
CVE-2025-9392 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 qosClassifier stack-based overflow — RE6250 8.8 High2025-08-24
CVE-2025-9363 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 portTriggerManageRule stack-based overflow — RE6250 8.8 High2025-08-23
CVE-2025-9362 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 urlFilterManageRule stack-based overflow — RE6250 6.3 Medium2025-08-23
CVE-2025-9361 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 ipRangeBlockManageRule stack-based overflow — RE6250 8.8 High2025-08-23
CVE-2025-9360 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 accessControlAdd stack-based overflow — RE6250 8.8 High2025-08-23
CVE-2025-9359 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 RP_checkCredentialsByBBS stack-based overflow — RE6250 8.8 High2025-08-23
CVE-2025-9358 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setSysAdm stack-based overflow — RE6250 8.8 High2025-08-23
CVE-2025-9357 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 langSwitchByBBS stack-based overflow — RE6250 8.8 High2025-08-23
CVE-2025-9356 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 inboundFilterAdd stack-based overflow — RE6250 8.8 High2025-08-22
CVE-2025-9355 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 scheduleAdd stack-based overflow — RE6250 8.8 High2025-08-22
CVE-2009-10006 UFO: Alien Invasion <= 2.2.1 IRC Client Buffer Overflow — UFO: Alien Invasion 8.8AIHighAI2025-08-22
CVE-2010-20122 Xftp FTP Client <= 3.0 PWD Response Buffer Overflow — Xftp FTP Client 8.8AIHighAI2025-08-21
CVE-2009-20003 Xenorate <= 2.50 .xpl File Stack-Based Buffer Overflow — Xenorate 7.8AIHighAI2025-08-21
CVE-2010-20114 VariCAD EN <= 2010-2.05 .dwb File Stack Buffer Overflow — VariCAD EN 7.8AIHighAI2025-08-21
CVE-2010-20123 Steinberg MyMP3Player <= 3.0.0.67 Buffer Overflow — MyMP3Player 7.8AIHighAI2025-08-21
CVE-2010-20007 Seagull FTP v3.3 Build 409 Stack Buffer Overflow — Seagull FTP Client 8.8AIHighAI2025-08-21
CVE-2009-20002 Millenium MP3 Studio <= 2.0 .pls File Stack-Based Buffer Overflow — MP3 Studio 7.8AIHighAI2025-08-21
CVE-2010-20034 Gekko Manager FTP Client <= 0.77 Stack Buffer Overflow — Gekko Manager FTP Client 9.8AICriticalAI2025-08-21
CVE-2009-20004 gAlan <= 0.2.1 Buffer Overflow — gAlan 7.8AIHighAI2025-08-21
CVE-2010-20108 FTPPad <= 1.2.0 Stack Buffer Overflow — FTPPad FTP Client 8.8AIHighAI2025-08-21

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