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-2023-43314 Zyxel PMG 安全漏洞 — PMG2005-T20B 7.5 High2023-09-27
CVE-2023-4260 Potential off-by-one buffer overflow vulnerability in the Zephyr FS subsystem — Zephyr 6.3 Medium2023-09-26
CVE-2023-4264 Potential buffer overflow vulnerabilities in the Zephyr Bluetooth subsystem — Zephyr 7.1 High2023-09-26
CVE-2023-4259 Potential buffer overflow vulnerabilities in the Zephyr eS-WiFi driver — Zephyr 7.1 High2023-09-25
CVE-2023-41299 Huawei HarmonyOS 安全漏洞 — HarmonyOS 7.5 -2023-09-25
CVE-2023-39409 Huawei HarmonyOS 安全漏洞 — HarmonyOS 7.5 -2023-09-25
CVE-2023-39408 Huawei HarmonyOS 安全漏洞 — HarmonyOS 7.5 -2023-09-25
CVE-2023-23364 Multimedia Console — Multimedia Console 8.1 High2023-09-22
CVE-2023-23363 QTS — QTS 8.1 High2023-09-22
CVE-2023-28562 Buffer Copy Without Checking Size of Input in QESL — Snapdragon 9.8 Critical2023-09-05
CVE-2023-28560 Buffer Copy Without Checking Size of Input in WLAN HAL — Snapdragon 7.8 High2023-09-05
CVE-2023-28559 Buffer Copy Without Checking Size of Input in WLAN HAL — Snapdragon 7.8 High2023-09-05
CVE-2023-28544 Buffer Copy without Checking the Size of Input in WLAN Firmware — Snapdragon 7.8 High2023-09-05
CVE-2023-21664 Buffer Copy without Checking the Size of Input(Classic Buffer Overflow) in Core Platform — Snapdragon 7.8 High2023-09-05
CVE-2023-21662 Buffer Copy without Checking the Size of Input(Classic Buffer Overflow) in Core Platform — Snapdragon 7.8 High2023-09-05
CVE-2023-40589 FreeRDP Global-Buffer-Overflow in ncrush_decompress — FreeRDP 4.3 Medium2023-08-31
CVE-2023-4163 Possible buffer overflow in portcfgfportbuffers in Brocade Fabric OS — Brocade Fabric OS 4.4 Medium2023-08-31
CVE-2023-24548 On affected platforms running Arista EOS with VXLAN configured, malformed or truncated packets received over a VXLAN tunnel and forwarded in hardware can cause egress ports to be unable to forward packets — EOS 5.3 Medium2023-08-29
CVE-2023-40166 Notepad++ heap buffer read overflow in FileManager::detectLanguageFromTextBegining — notepad-plus-plus 5.5 Medium2023-08-25
CVE-2023-40164 Notepad++ global buffer read overflow in nsCodingStateMachine::NextState — notepad-plus-plus 5.5 Medium2023-08-25
CVE-2023-40036 Notepad++ global buffer read overflow in CharDistributionAnalysis::HandleOneChar — notepad-plus-plus 5.5 Medium2023-08-25
CVE-2023-40031 Notepad++ vulnerable to heap buffer write overflow in Utf8_16_Read::convert — notepad-plus-plus 7.8 High2023-08-25
CVE-2022-3742 Lenovo notebook 安全漏洞 — Notebook 6.7 Medium2023-08-23
CVE-2023-20168 Cisco NX-OS Software 输入验证错误漏洞 — Cisco NX-OS Software 7.1 High2023-08-23
CVE-2023-4041 Second Stage Gecko Bootloader GBL Parser Buffer Overrun Vulnerability — Gecko Bootloader 9.8 Critical2023-08-23
CVE-2023-39454 ELECOM WRC-X1800GS-B 安全漏洞 — WRC-X1800GS-B 9.8 -2023-08-18
CVE-2023-34419 Lenovo Notebook 安全漏洞 — Lenovo Notebook 6.7 Medium2023-08-17
CVE-2023-4029 Lenovo ThinkPad 安全漏洞 — ThinkPad 6.7 Medium2023-08-17
CVE-2023-4028 Lenovo Notebook 安全漏洞 — Lenovo Notebook 6.7 Medium2023-08-17
CVE-2023-39386 Huawei HarmonyOS 输入验证错误漏洞 — HarmonyOS 7.5 -2023-08-13

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