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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-120 (未进行输入大小检查的缓冲区拷贝(传统缓冲区溢出)) — Vulnerability Class 1914

1914 vulnerabilities classified as CWE-120 (未进行输入大小检查的缓冲区拷贝(传统缓冲区溢出)). AI Chinese analysis included.

CWE-120 represents a critical memory safety vulnerability where software copies data into a fixed-size buffer without validating the input’s length against the destination’s capacity. This classic buffer overflow occurs when an attacker supplies input exceeding the allocated memory space, causing data to spill into adjacent memory regions. Exploitation typically involves injecting malicious code or altering program control flow, such as overwriting return addresses to execute arbitrary commands. Developers prevent this weakness by implementing rigorous bounds checking before any copy operation, ensuring the input size never exceeds the buffer’s limits. Utilizing safer, language-specific functions that automatically handle size verification, or adopting modern programming languages with built-in memory safety features, effectively mitigates this risk and preserves application integrity against memory corruption attacks.

MITRE CWE Description
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Common Consequences (2)
Integrity, Confidentiality, Availability Modify Memory, Execute Unauthorized Code or Commands
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of the product's implicit security policy. This can often be used to subvert any other security service.
Availability Modify Memory, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU)
Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the product into an infinite loop.
Mitigations (5)
Requirements Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a lan…
Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.
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
Implementation Consider adhering to the following rules when allocating and managing an application's memory: Double check that your buffer is as large as you specify. When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string. Check buffer boundaries if accessing the buffer i…
Implementation Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Examples (2)
The following code asks the user to enter their last name and then attempts to store the value entered in the last_name array.
char last_name[20]; printf ("Enter your last name: "); scanf ("%s", last_name);
Bad · C
The following code attempts to create a local copy of a buffer to perform some manipulations to the data.
void manipulate_string(char * string){ char buf[24]; strcpy(buf, string); ... }
Bad · C
CVE ID Title CVSS Severity Published
CVE-2024-0144 NVIDIA nvJPEG2000 安全漏洞 — nvJPEG2000 6.8 Medium 2025-02-12
CVE-2025-24956 Siemens OpenV2G 安全漏洞 — OpenV2G 6.2 Medium 2025-02-11
CVE-2025-1147 GNU Binutils nm nm.c internal_strlen buffer overflow — Binutils 3.1 Low 2025-02-10
CVE-2025-0303 Liteos_a has a buffer overflow vulnerability — OpenHarmony 8.8 High 2025-02-07
CVE-2025-23236 Humming Heads Defense Platform 安全漏洞 — Defense Platform Home Edition 7.7 - 2025-02-06
CVE-2025-23412 BIG-IP APM access profile vulnerability — BIG-IP 7.5 High 2025-02-05
CVE-2025-0960 AutomationDirect C-more EA9 HMI Classic Buffer Overflow — C-more EA9 HMI EA9-T6CL 9.8 Critical 2025-02-04
CVE-2024-23968 ChargePoint Home Flex SrvrToSmSetAutoChnlListMsg Stack-based Buffer Overflow — Home Flex 8.8 High 2025-01-30
CVE-2024-23973 Silicon Labs Gecko OS HTTP GET Request Handling Stack-based Buffer Overflow — Gecko OS 8.8 High 2025-01-30
CVE-2024-24731 Silicon Labs Gecko OS http_download Stack-based Buffer Overflow — Gecko OS 7.5 High 2025-01-30
CVE-2024-6351 Malformed packet leads to denial of service in NWK/APS layer — SiSDK 4.3 Medium 2025-01-28
CVE-2024-0146 NVIDIA vGPU Software 安全漏洞 — NVIDIA vGPU software 7.8 High 2025-01-28
CVE-2024-39750 IBM Analytics Content Hub buffer overflow — Analytics Content Hub 8.8 High 2025-01-25
CVE-2024-13503 Stack-Based Buffer Overflow in Newtec's update signaling causes RCE — NTC2218, NTC2250, NTC2299 9.8 - 2025-01-17
CVE-2024-36290 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 10.0 Critical 2025-01-14
CVE-2024-39769 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39288 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39770 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39768 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-37184 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39756 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39294 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39358 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-37357 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39774 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39370 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-36272 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39802 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39801 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-39299 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14

Vulnerabilities classified as CWE-120 (未进行输入大小检查的缓冲区拷贝(传统缓冲区溢出)) represent 1914 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.