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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1912 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, Availability Modify 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.
Availability Modify 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)
Requirements Use 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 Design Use 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 Compilation Use 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
Implementation Consider 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…
Implementation Assume 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 ID Title CVSS Severity Published
CVE-2026-6630 Tenda F451 httpd GstDhcpSetSer fromGstDhcpSetSer buffer overflow — F451 8.8 High 2026-04-20
CVE-2026-6581 H3C Magic B1 aspForm SetMobileAPInfoById buffer overflow — Magic B1 8.8 High 2026-04-19
CVE-2026-6563 H3C Magic B1 aspForm SetAPWifiorLedInfoById buffer overflow — Magic B1 8.8 High 2026-04-19
CVE-2026-6560 H3C Magic B0 aspForm Edit_BasicSSID buffer overflow — Magic B0 8.8 High 2026-04-19
CVE-2026-33337 Firebird has a buffer overflow when parsing corrupted slice packets — firebird 7.5 High 2026-04-17
CVE-2026-27820 zlib: Buffer Overflow in Zlib::GzipReader ungetc via large input leads to memory corruption — zlib 9.8 - 2026-04-16
CVE-2026-6384 Gimp: gimp: arbitrary code execution or denial of service via buffer overflow in gif image processing — Red Hat Enterprise Linux 6 7.3 High 2026-04-15
CVE-2026-6186 UTT HiPER 1200GW formNatStaticMap strcpy buffer overflow — HiPER 1200GW 8.8 High 2026-04-13
CVE-2026-34866 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.1 Medium 2026-04-13
CVE-2026-6157 Totolink A800R app.so setAppEasyWizardConfig buffer overflow — A800R 8.8 High 2026-04-13
CVE-2026-6014 D-Link DIR-513 POST Request formAdvanceSetup buffer overflow — DIR-513 8.8 High 2026-04-10
CVE-2026-6013 D-Link DIR-513 POST Request formSetRoute buffer overflow — DIR-513 8.8 High 2026-04-10
CVE-2026-6012 D-Link DIR-513 POST Request formSetPassword buffer overflow — DIR-513 8.8 High 2026-04-10
CVE-2026-5984 D-Link DIR-605L POST Request formSetLog buffer overflow — DIR-605L 8.8 High 2026-04-09
CVE-2026-5983 D-Link DIR-605L POST Request formSetDDNS buffer overflow — DIR-605L 8.8 High 2026-04-09
CVE-2026-5982 D-Link DIR-605L POST Request formAdvNetwork buffer overflow — DIR-605L 8.8 High 2026-04-09
CVE-2025-59969 Junos OS Evolved: QFX5000 Series and PTX Series: An attacker sending crafted multicast packets will cause evo-aftmand / evo-pfemand to crash and restart — Junos OS Evolved 6.5 Medium 2026-04-09
CVE-2026-5981 D-Link DIR-605L POST Request formAdvFirewall buffer overflow — DIR-605L 8.8 High 2026-04-09
CVE-2026-5980 D-Link DIR-605L POST Request formSetMACFilter buffer overflow — DIR-605L 8.8 High 2026-04-09
CVE-2026-5979 D-Link DIR-605L POST Request formVirtualServ buffer overflow — DIR-605L 8.8 High 2026-04-09
CVE-2026-21382 Buffer Copy Without Checking Size of Input in Power Management IC — Snapdragon 7.8 High 2026-04-06
CVE-2025-47389 Buffer Copy Without Checking Size of Input in Automotive Platform — Snapdragon 7.8 High 2026-04-06
CVE-2026-5567 Tenda M3 Destination setAdvPolicyData buffer overflow — M3 8.8 High 2026-04-05
CVE-2026-5566 UTT HiPER 1250GW formNatStaticMap strcpy buffer overflow — HiPER 1250GW 8.8 High 2026-04-05
CVE-2018-25237 Hirschmann HiSecOS Buffer Overflow via HTTPS Login — Hirschmann HiSecOS Classic Firewall (EAGLE, EAGLE One) 9.8 Critical 2026-04-03
CVE-2026-34124 Denial of Service via Path Expansion Overflow in HTTP Service in TP-Link Tapo C520WS — Tapo C520WS v2.6 6.5AI Medium AI 2026-04-02
CVE-2026-5164 Virtio-win: virtio-win: denial of service via unvalidated descriptor count in unmap request — Red Hat Enterprise Linux 10 6.7 Medium 2026-03-30
CVE-2026-1679 net: eswifi socket send payload length not bounded — Zephyr 7.3 High 2026-03-27
CVE-2026-4976 Totolink LR350 cstecgi.cgi setWiFiGuestCfg buffer overflow — LR350 8.8 High 2026-03-27
CVE-2026-4862 UTT HiPER 1250GW Parameter formConfigDnsFilterGlobal strcpy buffer overflow — HiPER 1250GW 8.8 High 2026-03-26

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