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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

3240 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)
Availability Modify 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 Control Modify 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, Other Modify 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 Compilation Use 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 Design Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation Implement and perform bounds checking on input.
Implementation Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors.
Operation, Build and Compilation Run 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 ID Title CVSS Severity Published
CVE-2023-25111 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25110 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25109 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25108 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25107 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25106 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25105 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25104 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25103 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25102 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25101 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25100 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25099 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25098 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25097 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25096 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25095 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25094 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25093 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25092 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25091 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25090 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25089 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25088 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25087 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25086 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25085 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25084 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25083 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06
CVE-2023-25082 Milesight UR32L 缓冲区错误漏洞 — UR32L 7.2 High 2023-07-06

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