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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1810 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, AvailabilityModify 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.
AvailabilityModify 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)
RequirementsUse 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 DesignUse 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 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
ImplementationConsider 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…
ImplementationAssume 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 IDTitleCVSSSeverityPublished
CVE-2024-6564 Buffer overflow in Rensas RCAR — rcar_gen3_v2.5 6.7 Medium2024-07-08
CVE-2024-23368 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Qualcomm IPC — Snapdragon 7.8 High2024-07-01
CVE-2024-39349 Synology Camera Firmware 安全漏洞 — Camera Firmware 9.8 Critical2024-06-28
CVE-2024-4640 OnCell G3470A-LTE Series: Authenticated Command Injection via sendTestEmail — OnCell G3150A-LTE Series 7.1 High2024-06-25
CVE-2024-6143 Actiontec WCB6200Q uh_tcp_recv_header Buffer Overflow Remote Code Execution Vulnerability — WCB6200Q 8.8 -2024-06-18
CVE-2024-6142 Actiontec WCB6200Q uh_tcp_recv_content Buffer Overflow Remote Code Execution Vulnerability — WCB6200Q 8.8 -2024-06-18
CVE-2024-37305 Buffer overflow in deserialization in oqs-provider — oqs-provider 8.2 High2024-06-17
CVE-2024-0099 CVE — vGPU software and Cloud Gaming 7.8 High2024-06-13
CVE-2024-37040 Schneider Electric SAGE RTUs 安全漏洞 — Sage 1410 5.4 Medium2024-06-12
CVE-2024-5463 Synology Camera Firmware 安全漏洞 — Camera Firmware 6.5 Medium2024-06-04
CVE-2023-43556 Buffer Copy Without Checking Size of Input in Hypervisor — Snapdragon 9.3 Critical2024-06-03
CVE-2023-43542 Buffer Copy Without Checking Size of Input in Trusted Execution Environment — Snapdragon 7.8 High2024-06-03
CVE-2023-43538 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in TZ Secure OS — Snapdragon 9.3 Critical2024-06-03
CVE-2024-5564 Libndp: buffer overflow in route information length field 8.1 High2024-05-31
CVE-2022-4969 bwoodsend rockhopper Binary Parser ragged_array.c count_rows buffer overflow — rockhopper 5.3 Medium2024-05-27
CVE-2024-5243 TP-Link Omada ER605 Buffer Overflow Remote Code Execution Vulnerability — Omada ER605 7.5AIHighAI2024-05-23
CVE-2024-27130 QTS, QuTS hero — QTS 7.2 High2024-05-21
CVE-2024-27129 QTS, QuTS hero — QTS 6.4 Medium2024-05-21
CVE-2024-27128 QTS, QuTS hero — QTS 6.4 Medium2024-05-21
CVE-2024-0816 Zyxel DX3300-T1 安全漏洞 — DX3300-T1 firmware 5.5 Medium2024-05-21
CVE-2023-37929 Zyxel VMG3625-T50B 安全漏洞 — V5.50(ABPM.8)C0 firmware 6.5 Medium2024-05-21
CVE-2024-30259 FastDDS heap buffer overflow when publisher sends malformed packet — Fast-DDS 8.2 High2024-05-13
CVE-2024-22472 Long S0 frames received by 500 series Z-Wave devices may cause buffer overflow — Z-Wave SDK 8.1 High2024-05-07
CVE-2024-21480 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Audio — Snapdragon 7.3 High2024-05-06
CVE-2023-43526 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Audio — Snapdragon 6.7 Medium2024-05-06
CVE-2023-43525 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Audio — Snapdragon 6.7 Medium2024-05-06
CVE-2023-43524 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Audio — Snapdragon 6.7 Medium2024-05-06
CVE-2024-4511 Shanghai Sunfull Automation BACnet Server HMI1002-ARM Message buffer overflow — BACnet Server HMI1002-ARM 6.3 Medium2024-05-06
CVE-2024-32018 Ineffective size check due to assert() and buffer overflow in RIOT — RIOT 8.8 High2024-05-01
CVE-2024-32017 Buffer overflows in RIOT — RIOT 9.8 Critical2024-05-01

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