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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1889 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-2026-19969 Open Asset Import Library Assimp 3DGS MDL7 Model Output Mesh Generator MDLLoader.cpp GenerateOutputMeshes_3DGS_MDL7 buffer overflow — Assimp 5.4 Medium2026-08-17
CVE-2026-19961 Edimax EW-7478APC formWlSiteSurvey buffer overflow — EW-7478APC 9.9 Critical2026-08-16
CVE-2026-19821 Tenda AC12 httpd web management interface SetSysAutoRebbotCfg formSetRebootTimer buffer overflow — AC12 8.8 High2026-08-14
CVE-2026-19792 Tenda G0 httpd web management interface module setPortMapping buffer overflow — G0 8.8 High2026-08-14
CVE-2026-17220 IBM i is Affected By Multiple Vulnerabilities in Host Servers — i 8.2 High2026-08-13
CVE-2026-19002 Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver — BI Connector ODBC Driver 8.1 High2026-08-12
CVE-2026-70465 Fortinet forticlientwindows 缓冲区错误漏洞 — FortiClientWindows 7.3 High2026-08-12
CVE-2025-41769 Unauthenticated Buffer Overflow in PROFINET Service — AXC F 1152 9.8 Critical2026-08-12
CVE-2024-14044 Open5GS Diameter Rx pcrf-rx-path.c pcrf_rx_aar_cb buffer overflow — Open5GS 6.3 Medium2026-08-12
CVE-2026-15565 Undertow: undertow-websockets: undertow: pre-auth dos on websocket endpoint with @serverendpoint class with any @onmessage method — Red Hat JBoss Enterprise Application Platform 7.4.25 7.5 High2026-08-11
CVE-2026-71958 D-Link DWR-M961 Buffer Overflow via quicksetup.cgi — DWR-M961 9.8 Critical2026-08-08
CVE-2026-71957 D-Link DWR-M961 Buffer Overflow via app.cgi — DWR-M961 9.8 Critical2026-08-08
CVE-2026-20348 ClamAV XAR File Format Processing Memory Corruption Vulnerability — Cisco Secure Endpoint 7.5 High2026-08-07
CVE-2026-20337 ClamAV ZIP File Format Processing Memory Corruption Vulnerability — Cisco Secure Endpoint 7.5 High2026-08-07
CVE-2026-18103 Dhcp-server: dhcp-server: persistent denial of service due to buffer overflow via omapi — Red Hat Enterprise Linux 6 4.9 Medium2026-08-04
CVE-2026-45537 OpenSIPS: Global Buffer Overflow in construct_uri — opensips 9.1 Critical2026-08-04
CVE-2026-45100 OpenSIPS: Buffer Overflow in Base64 Encode Transformation — opensips 9.1 Critical2026-08-04
CVE-2026-15314 Authenticated Denial-of-Service Vulnerability in TP-Link Tapo P110 — P110 v1 7.1 High2026-08-04
CVE-2026-24080 Buffer Copy Without Checking Size of Input in Biometrics — Snapdragon 7.8 High2026-08-04
CVE-2026-24076 Buffer Copy Without Checking Size of Input in Bluetooth HOST — Snapdragon 6.7 Medium2026-08-04
CVE-2026-6694 Gimp: gimp file-png plugin: denial of service via oversized apng trns chunk — Red Hat Enterprise Linux 6 5.5 Medium2026-08-03
CVE-2026-18321 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in ntpsec — ntpsec 4.7 Medium2026-07-31
CVE-2026-11885 Power System update in Buffer Copy — PowerVM Hypervisor 8.4 High2026-07-30
CVE-2026-59250 Megaco flex scanner buffer overflow via oversized property parm name — OTP 8.3 High2026-07-27
CVE-2026-45811 Apache NimBLE: Buffer overflow in socket HCI transport — Apache NimBLE--2026-07-24
CVE-2026-44436 Quicly is vulnerable to connection state corruption — quicly 7.5 High2026-07-16
CVE-2026-58553 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 4.0 Medium2026-07-15
CVE-2026-58552 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 5.1 Medium2026-07-15
CVE-2026-58551 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 5.1 Medium2026-07-15
CVE-2026-58550 Huawei HarmonyOS 缓冲区错误漏洞 — HarmonyOS 4.0 Medium2026-07-15

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