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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

2567 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-2011-10016 Real Networks Netzip Classic 7.5.1.86 File Parsing Buffer Overflow — Netzip Classic 7.8AIHighAI2025-08-13
CVE-2012-10058 RabidHamster R4 Log Entry sprintf() Buffer Overflow — R4 Embedded Server 9.8AICriticalAI2025-08-13
CVE-2011-10012 NetOp Remote Control Client 9.5 .dws File Buffer Overflow — Remote Control Client 7.8AIHighAI2025-08-13
CVE-2012-10057 Lattice Semiconductor ispVM System 18.0.2 XCF File Handling Buffer Overflow — ispVM System 7.8AIHighAI2025-08-13
CVE-2011-10014 GTA SA-MP server.cfg Buffer Overflow — San Andreas Multiplayer 7.3AIHighAI2025-08-13
CVE-2011-10015 Cytel Studio <= 9.0 .CY3 File Stack Buffer Overflow — Cytel Studio 7.8AIHighAI2025-08-13
CVE-2025-46405 BIG-IP APM vulnerability — BIG-IP 7.5 High2025-08-13
CVE-2025-32766 Fortinet FortiWeb CLI 安全漏洞 — FortiWeb 6.3 Medium2025-08-12
CVE-2025-49564 Illustrator | Stack-based Buffer Overflow (CWE-121) — Illustrator 7.8 High2025-08-12
CVE-2025-8851 LibTIFF tiffcrop tiffcrop.c readSeparateStripsetoBuffer stack-based overflow — LibTIFF 5.3 Medium2025-08-11
CVE-2025-8846 NASM Netwide Assember parser.c parse_line stack-based overflow — Netwide Assember 5.3 Medium2025-08-11
CVE-2025-8845 NASM Netwide Assember nasm.c assemble_file stack-based overflow — Netwide Assember 5.3 Medium2025-08-11
CVE-2025-8833 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 langSwitchBack stack-based overflow — RE6250 8.8 High2025-08-11
CVE-2025-8832 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setDMZ stack-based overflow — RE6250 8.8 High2025-08-11
CVE-2025-8831 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 remoteManagement stack-based overflow — RE6250 8.8 High2025-08-11
CVE-2025-8826 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 RP_setBasicAuto um_rp_autochannel stack-based overflow — RE6250 8.8 High2025-08-11
CVE-2025-8824 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setRIP stack-based overflow — RE6250 8.8 High2025-08-11
CVE-2025-8822 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setOpMode algDisable stack-based overflow — RE6250 8.8 High2025-08-11
CVE-2025-8820 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 wirelessBasic stack-based overflow — RE6250 8.8 High2025-08-10
CVE-2025-8819 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setWan stack-based overflow — RE6250 8.8 High2025-08-10
CVE-2025-8817 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setLan stack-based overflow — RE6250 8.8 High2025-08-10
CVE-2025-8816 Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setOpMode stack-based overflow — RE6250 8.8 High2025-08-10
CVE-2025-8810 Tenda AC20 SetFirewallCfg strcpy stack-based overflow — AC20 8.8 High2025-08-10
CVE-2012-10053 Simple Web Server Connection Header Buffer Overflow — Simple Web Server 9.8 -2025-08-08
CVE-2012-10051 Photodex ProShow Producer 5.0.3256 load File Handling Buffer Overflow — ProShow Producer 7.3 -2025-08-08
CVE-2012-10043 ActFax 4.32 Client Importer Buffer Overflow — Server 7.8 -2025-08-08
CVE-2025-23311 NVIDIA Triton Inference Server 安全漏洞 — Triton Inference Server 9.8 Critical2025-08-06
CVE-2025-23310 NVIDIA Triton Inference Server 安全漏洞 — Triton Inference Server 9.8 Critical2025-08-06
CVE-2025-54617 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.8 Medium2025-08-06
CVE-2025-8653 Kenwood DMX958XR JKRadioService Stack-based Buffer Overflow Remote Code Execution Vulnerability — DMX958XR 8.8AIHighAI2025-08-06

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