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-39803 WAVLINK AC3000 安全漏洞 — Wavlink AC3000 9.1 Critical 2025-01-14
CVE-2024-6352 Malformed packet leads to denial of service in APS layer — SiSDK 4.3 Medium 2025-01-13
CVE-2024-6350 EmberZNet malformed MAC layer packet leads to denial of service — Simplicity SDK 6.5 Medium 2025-01-08
CVE-2024-56456 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.8 Medium 2025-01-08
CVE-2024-56455 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium 2025-01-08
CVE-2024-56454 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium 2025-01-08
CVE-2024-56453 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.8 Medium 2025-01-08
CVE-2024-56452 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium 2025-01-08
CVE-2024-56450 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.3 Medium 2025-01-08
CVE-2024-45547 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in WLAN Windows Host — Snapdragon 7.8 High 2025-01-06
CVE-2024-45541 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in WLAN Windows Host — Snapdragon 7.8 High 2025-01-06
CVE-2024-21464 Buffer Copy Without Checking Size of Input in Data Network Stack & Connectivity — Snapdragon 8.4 High 2025-01-06
CVE-2024-12988 Netgear R6900P/R7000P HTTP Header sub_16C4C buffer overflow — R6900P 7.3 High 2024-12-27
CVE-2024-47864 Sharp HR02、Sharp SH-52B和Sharp SH-54C 安全漏洞 — home 5G HR02 7.5 - 2024-12-23
CVE-2020-6923 HP Linux Imaging and Printing Software - Potential Memory Buffer Overflow — HP Linux Imaging and Printing Software 5.7 Medium 2024-12-19
CVE-2024-12194 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High 2024-12-17
CVE-2024-52066 Potential stack corruption in Routing Service when using a malicious XML configuration document — Connext Professional 9.1 - 2024-12-13
CVE-2024-52065 Potential stack buffer write overflow in Persistence Service while parsing malicious environment variable on non-Windows systems — Connext Professional 8.4 - 2024-12-13
CVE-2024-52064 Potential stack buffer write overflow in Connext applications while parsing malicious license file — Connext Professional 9.1 - 2024-12-13
CVE-2024-52063 Potential stack buffer write overflow in Connext applications while parsing malicious XML types document — Connext Professional 9.8 - 2024-12-13
CVE-2024-52062 Potential stack buffer write overflow in Connext applications while parsing malicious XML types document — Connext Professional 9.1 - 2024-12-13
CVE-2024-52061 Potential stack buffer overflow when parsing an XML type — Connext Professional 9.8 - 2024-12-13
CVE-2024-52060 Potential stack overflow when using XML configuration file referencing environment variables — Connext Professional 9.8 - 2024-12-13
CVE-2024-52059 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), Heap-based Buffer Overflow, Integer Overflow or Wraparound vulnerability in RTI Connext Professional (Security Plugins) allows Overflow Variables and Tags. — Connext Professional 9.1 - 2024-12-13
CVE-2024-54105 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.1 Medium 2024-12-12
CVE-2024-12354 SourceCodester Phone Contact Manager System User Menu MenuDisplayStart buffer overflow — Phone Contact Manager System 5.3 Medium 2024-12-09
CVE-2024-12343 TP-Link VN020 F3v(T) SOAP Request WANIPConnection buffer overflow — VN020 F3v(T) 6.5 Medium 2024-12-08
CVE-2024-12147 Netgear R6900 HTTP Header upgrade_check.cgi buffer overflow — R6900 6.5 Medium 2024-12-04
CVE-2024-9197 Zyxel VMG3625-T50B 安全漏洞 — VMG3625-T50B firmware 4.9 Medium 2024-12-03
CVE-2024-8748 Zyxel VMG8825-T50K 安全漏洞 — VMG8825-T50K firmware 7.5 High 2024-12-03

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