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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1815 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-2022-33259 Buffer copy without checking the size of input in Modem — Snapdragon 9.8 Critical2023-04-04
CVE-2022-25740 Buffer Copy Without Checking Size of Input in MODEM — Snapdragon 9.8 Critical2023-04-04
CVE-2022-25678 Buffer Copy Without Checking Size of Input in MODEM — Snapdragon 9.8 Critical2023-04-04
CVE-2023-0977 Trellix Agent 缓冲区错误漏洞 — Trellix Agent 6.7 Medium2023-04-03
CVE-2023-25076 SNIProxy 安全漏洞 — SNIProxy 9.8 Critical2023-03-30
CVE-2023-28508 Heap corruption in UniRPC service — UniData 8.8 -2023-03-29
CVE-2023-28506 Stack buffer overflow in UniRPC service — UniData 8.8 -2023-03-29
CVE-2023-28505 Buffer overflow in UniRPC library function — UniData 8.8 -2023-03-29
CVE-2023-28504 Stack buffer overflow in UniRPC library function — UniData 8.8 -2023-03-29
CVE-2023-28502 Stack buffer overflow in UniRPC's udadmin_server service — UniData 9.8 -2023-03-29
CVE-2022-27643 NETGEAR R6700v3 授权问题漏洞 — R6700v3 8.8 -2023-03-29
CVE-2022-42431 Tesla 安全漏洞 — Model 3 7.8 -2023-03-29
CVE-2023-25664 TensorFlow vulnerable to Heap Buffer Overflow in AvgPoolGrad — tensorflow 7.5 High2023-03-24
CVE-2023-1560 TinyTIFF File tinytiffreader.c buffer overflow — TinyTIFF 2.8 Low2023-03-22
CVE-2023-28116 Buffer overflow in L2CAP due to misconfigured MTU — contiki-ng 8.1 High2023-03-17
CVE-2023-1452 GPAC load_text.c buffer overflow — GPAC 5.3 Medium2023-03-17
CVE-2023-26109 npm node-bluetooth 安全漏洞 — node-bluetooth-serial-port 7.3 High2023-03-09
CVE-2023-26110 npm node-bluetooth 安全漏洞 — node-bluetooth 7.3 High2023-03-09
CVE-2022-40540 Buffer copy without checking the size of input in Linux Kernel — Snapdragon 8.4 High2023-03-07
CVE-2022-33278 Buffer copy without checking the size of input in HLOS — Snapdragon 7.8 High2023-03-07
CVE-2022-25655 Buffer copy without checking the size of input in WLAN HAL. — Snapdragon 8.4 High2023-03-07
CVE-2023-1190 xiaozhuai imageinfo imageinfo.hpp buffer overflow — imageinfo 4.8 Medium2023-03-06
CVE-2023-0996 libheif 安全漏洞 — libheif 7.8 -2023-02-24
CVE-2023-24809 NetHack Call command buffer overflow — NetHack 5.5 Medium2023-02-17
CVE-2023-20032 ClamAV 缓冲区错误漏洞 — Cisco Secure Web Appliance 9.8 Critical2023-02-16
CVE-2023-24482 Siemens Comos 安全漏洞 — COMOS V10.2 10.0 Critical2023-02-14
CVE-2022-40514 Buffer copy without checking size of input in WLAN Firmware — Snapdragon 9.8 Critical2023-02-09
CVE-2022-33277 Buffer copy without checking size of input in modem — Snapdragon 8.4 High2023-02-09
CVE-2022-33232 Buffer copy without checking size of input in Hypervisor — Snapdragon 9.3 Critical2023-02-09
CVE-2023-0687 GNU C Library 安全漏洞 — C Library 4.6 Medium2023-02-06

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