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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1805 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-2021-34987 Corel Parallels Desktop 权限许可和访问控制问题漏洞 — Desktop 8.2 -2022-07-15
CVE-2022-34756 Schneider Electric Easergy P5 安全漏洞 — Easergy P5 8.8 High2022-07-13
CVE-2022-26649 多款Siemens SCALANCE产品安全漏洞 — SCALANCE X200-4P IRT 9.6 Critical2022-07-12
CVE-2022-26648 Siemens SCALANCE 安全漏洞 — SCALANCE X200-4P IRT 8.2 High2022-07-12
CVE-2022-32140 CODESYS runtime system prone to denial of service due to buffer copy — Runtime Toolkit 6.5 Medium2022-06-24
CVE-2022-21742 Realtek USB FE/1GbE/2.5GbE/5GbE NIC Family - Buffer Overflow — USB FE/1GbE/2.5GbE/5GbE NIC Family 6.2 Medium2022-06-20
CVE-2022-31626 mysqlnd/pdo password buffer overflow — PHP 7.5 High2022-06-16
CVE-2022-31031 Potential stack buffer overflow when parsing message as a STUN client — pjproject 9.8 Critical2022-06-07
CVE-2022-31019 DoS Vulnerability in URLEncodedFormDecoder in Vapor — vapor 7.5 High2022-06-06
CVE-2022-31482 Denial-of-Service via internal structure overflow — LNL-X2210 7.5 High2022-06-06
CVE-2022-31481 Remote Code Execution via buffer overflow in firmware update process — LNL-X2210 10.0 Critical2022-06-06
CVE-2021-3555 Eufy Indoor 2K Indoor Camera 安全漏洞 — Indoor 2K Indoor Camera 7.6 High2022-05-31
CVE-2022-29246 Potential buffer overflow in function DFU upload in Azure RTOS USBX — usbx 9.8 Critical2022-05-24
CVE-2022-29242 Buffer Overflow on creating key transport blob in GOST Engine — engine 5.9 Medium2022-05-24
CVE-2022-29223 Buffer overflow on HUB descriptor in Azure RTOS USBX — usbx 7.5 High2022-05-24
CVE-2022-29189 Buffer for inbound DTLS fragments has no limit — dtls 5.3 Medium2022-05-20
CVE-2022-29210 Heap buffer overflow due to incorrect hash function in TensorFlow — tensorflow 5.5 Medium2022-05-20
CVE-2022-1110 Lenovo Smart Standby Driver 安全漏洞 — Smart Standby Driver 5.5 Medium2022-05-18
CVE-2022-1735 Classic Buffer Overflow in vim/vim — vim/vim 7.8 -2022-05-17
CVE-2021-22275 Denial of service vulnerability on Automation Runtime webserver — Automation Runtime webserver 8.6 High2022-05-13
CVE-2022-24910 InHand Networks InRouter302 缓冲区错误漏洞 — InRouter302 7.8 -2022-05-12
CVE-2022-27242 OpenV2G 安全漏洞 — OpenV2G 5.5 -2022-05-10
CVE-2022-24903 Buffer overflow in TCP syslog server (receiver) components in rsyslog — rsyslog 8.1 High2022-05-05
CVE-2022-0636 Lenovo Thin Installer 输入验证错误漏洞 — Thin Installer 5.0 Medium2022-04-22
CVE-2021-21967 Sealevel Systems SeaConnect 370W 缓冲区错误漏洞 — SeaConnect 370W 5.9 -2022-04-14
CVE-2021-21939 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 8.8 -2022-04-14
CVE-2022-24788 Buffer overflow in Vyper — vyper 7.1 High2022-04-13
CVE-2022-26335 多款 Siemens 产品安全漏洞 — SCALANCE X302-7 EEC (230V) 7.5 -2022-04-12
CVE-2022-26334 Siemens SCALANCE安全漏洞 — SCALANCE X302-7 EEC (230V) 7.5 -2022-04-12
CVE-2022-26414 Zyxel VMG3312-T20A 安全漏洞 — VMG3312-T20A firmware 6.0 Medium2022-04-11

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