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-2022-42283 NVIDIA BMC 安全漏洞 — NVIDIA DGX servers 6.4 Medium2023-01-13
CVE-2022-42274 NVIDIA BMC 安全漏洞 — NVIDIA DGX servers 7.8 High2023-01-13
CVE-2022-42273 NVIDIA BMC 安全漏洞 — NVIDIA DGX servers 8.1 High2023-01-12
CVE-2022-42272 NVIDIA BMC 安全漏洞 — NVIDIA DGX servers 8.1 High2023-01-12
CVE-2023-22399 Junos OS: QFX10K Series: PFE crash upon receipt of specific genuine packets when sFlow is enabled — Junos OS 7.5 High2023-01-12
CVE-2023-22416 Junos OS: MX Series and SRX Series: The flow processing daemon (flowd) will crash if SIP ALG is enabled and a malformed SIP packet is received — Junos OS 7.5 High2023-01-12
CVE-2017-14454 HTTPS 安全漏洞 — Hub 9.9 -2023-01-11
CVE-2022-42271 NVIDIA BMC 安全漏洞 — NVIDIA DGX Servers 8.4 High2023-01-11
CVE-2022-43389 Zyxel NR7101 安全漏洞 — NR7101 firmware 8.6 High2023-01-11
CVE-2022-43391 Zyxel NR7101 安全漏洞 — NR7101 firmware 6.5 Medium2023-01-11
CVE-2022-43392 Zyxel NR7101 安全漏洞 — NR7101 firmware 6.5 Medium2023-01-11
CVE-2022-43662 Kernel subsystem in kernel_liteos_a has a kernel stack overflow vulnerability when call SysTimerGettime. — OpenHarmony 4.0 Medium2023-01-09
CVE-2022-45126 Kernel subsystem in kernel_liteos_a has a kernel stack overflow vulnerability when call SysClockGettime. — OpenHarmony 4.0 Medium2023-01-09
CVE-2022-43970 Buffer overflow in Linksys WRT54GL — WRT54GL Wireless-G Broadband Router 7.2 High2023-01-09
CVE-2022-39118 UNISOC chipset 缓冲区错误漏洞 — SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8000 5.5 -2023-01-04
CVE-2022-4857 Modbus Tools Modbus Poll mbp File mbpoll.exe buffer overflow — Modbus Poll 6.3 Medium2022-12-30
CVE-2022-4856 Modbus Tools Modbus Slave mbs File mbslave.exe buffer overflow — Modbus Slave 6.3 Medium2022-12-30
CVE-2022-42261 NVIDIA vGPU Software 安全漏洞 — vGPU software (Virtual GPU Manager), NVIDIA Cloud Gaming (Virtual GPU Manager) 7.8 High2022-12-30
CVE-2022-41966 XStream Denial of Service via stack overflow — xstream 8.2 High2022-12-27
CVE-2022-23477 Buffer Overflow in xrdp — xrdp 9.1 Critical2022-12-09
CVE-2022-23480 Buffer Overflow in xrdp — xrdp 9.1 Critical2022-12-09
CVE-2022-23479 Buffer Overflow occurs in xrdp — xrdp 9.1 Critical2022-12-09
CVE-2022-23468 Buffer Overflow in xrdp — xrdp 6.5 Medium2022-12-09
CVE-2022-46824 JetBrains IntelliJ IDEA 安全漏洞 — IntelliJ IDEA 5.6 Medium2022-12-08
CVE-2022-41802 Kernel subsystem in kernel_liteos_a has a kernel stack overflow vulnerability when call SysClockGetres. — OpenHarmony 4.0 Medium2022-12-08
CVE-2022-44455 The appspawn and nwebspawn services were found to be vulnerable to buffer overflow vulnerability due to insufficient input validation. — OpenHarmony 6.8 Medium2022-12-08
CVE-2022-20687 Cisco ATA 190 输入验证错误漏洞 — Cisco Analog Telephone Adaptor (ATA) Software 5.3 Medium2022-12-07
CVE-2022-42756 Google Pixel 安全漏洞 — SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8000 5.5 -2022-12-06
CVE-2022-42760 UNISOC chipset 安全漏洞 — SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8018 5.5 -2022-12-06
CVE-2022-4172 QEMU 安全漏洞 — QEMU (ACPI ERST) 6.5 -2022-11-29

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