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-11960 D-Link DIR-605L formSetPortTr buffer overflow — DIR-605L 8.8 High 2024-11-28
CVE-2024-11959 D-Link DIR-605L formResetStatistic buffer overflow — DIR-605L 8.8 High 2024-11-28
CVE-2024-47248 Apache NimBLE: Buffer overflow in NimBLE MESH Bluetooth stack — Apache NimBLE 9.8AI Critical AI 2024-11-26
CVE-2024-37041 QTS, QuTS hero — QTS 7.2 - 2024-11-22
CVE-2024-37044 QTS, QuTS hero — QTS 7.2 - 2024-11-22
CVE-2024-37047 QTS, QuTS hero — QTS 7.2 - 2024-11-22
CVE-2024-37049 QTS, QuTS hero — QTS 7.2 - 2024-11-22
CVE-2024-37050 QTS, QuTS hero — QTS 7.2 - 2024-11-22
CVE-2021-1379 Cisco IP Phones Cisco Discovery Protocol and Link Layer Discovery Protocol Remote Code Execution and Denial of Service Vulnerabilities — Cisco IP Phones with Multiplatform Firmware 6.5 Medium 2024-11-18
CVE-2022-20846 Cisco IOS XR Software Cisco Discovery Protocol Buffer Overflow Vulnerability — Cisco IOS XR Software 4.3 Medium 2024-11-15
CVE-2024-8882 Zyxel GS1900 安全漏洞 — GS1900-48 firmware 4.5 Medium 2024-11-12
CVE-2024-10964 emqx neuron plugin_handle.c handle_add_plugin buffer overflow — neuron 6.3 Medium 2024-11-07
CVE-2024-38423 Buffer Copy Without Checking Size of Input in Graphics Linux — Snapdragon 7.8 High 2024-11-04
CVE-2024-38409 Buffer Copy Without Checking Size of Input in WLAN Windows Host — Snapdragon 7.8 High 2024-11-04
CVE-2024-33030 Buffer Copy without Checking Size of Input (`Classic Buffer Overflow`) in Performance — Snapdragon 6.7 Medium 2024-11-04
CVE-2024-10559 SourceCodester Airport Booking Management System details buffer overflow — Airport Booking Management System 5.3 Medium 2024-10-31
CVE-2024-9997 Autodesk AutoCAD DWG File Parsing Memory Corruption Code Execution Vulnerability — AutoCAD 7.8 High 2024-10-29
CVE-2024-8592 Autodesk AutoCAD CATPART File Parsing Memory Corruption Code Execution Vulnerability — AutoCAD 7.8 High 2024-10-29
CVE-2024-10371 SourceCodester Payroll Management System main login buffer overflow — Payroll Management System 6.3 Medium 2024-10-25
CVE-2024-9915 D-Link DIR-619L B1 formVirtualServ buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9914 D-Link DIR-619L B1 formSetWizardSelectMode buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9913 D-Link DIR-619L B1 formSetRoute buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9912 D-Link DIR-619L B1 formSetQoS buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9911 D-Link DIR-619L B1 formSetPortTr buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9910 D-Link DIR-619L B1 formSetPassword buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9909 D-Link DIR-619L B1 formSetMuti buffer overflow — DIR-619L B1 8.8 High 2024-10-13
CVE-2024-9908 D-Link DIR-619L B1 formSetMACFilter buffer overflow — DIR-619L B1 5.5 Medium 2024-10-13
CVE-2024-9786 D-Link DIR-619L B1 formSetLog buffer overflow — DIR-619L B1 8.8 High 2024-10-10
CVE-2024-9785 D-Link DIR-619L B1 formSetDDNS buffer overflow — DIR-619L B1 8.8 High 2024-10-10
CVE-2024-9784 D-Link DIR-619L B1 formResetStatistic buffer overflow — DIR-619L B1 8.8 High 2024-10-10

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