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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1914 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-2025-8245 TOTOLINK X15 HTTP POST Request formMultiAPVLAN buffer overflow — X15 8.8 High 2025-07-27
CVE-2025-8244 TOTOLINK X15 HTTP POST Request formMapDelDevice buffer overflow — X15 8.8 High 2025-07-27
CVE-2025-8243 TOTOLINK X15 HTTP POST Request formMapDel buffer overflow — X15 8.8 High 2025-07-27
CVE-2025-8242 TOTOLINK X15 HTTP POST Request formFilter buffer overflow — X15 8.8 High 2025-07-27
CVE-2025-8180 Tenda CH22 deleteUserName formdeleteUserName buffer overflow — CH22 8.8 High 2025-07-26
CVE-2025-8177 LibTIFF thumbnail.c setrow buffer overflow — LibTIFF 5.3 Medium 2025-07-26
CVE-2025-8170 TOTOLINK T6 MQTT Packet meshSlaveDlfw tcpcheck_net buffer overflow — T6 8.8 High 2025-07-25
CVE-2025-8169 D-Link DIR-513 HTTP POST Request formSetWanPPTPpath formSetWanPPTPcallback buffer overflow — DIR-513 8.8 High 2025-07-25
CVE-2025-8168 D-Link DIR-513 formSetWanPPPoE websAspInit buffer overflow — DIR-513 8.8 High 2025-07-25
CVE-2025-8160 Tenda AC20 httpd SetSysTimeCfg buffer overflow — AC20 8.8 High 2025-07-25
CVE-2025-8140 TOTOLINK A702R HTTP POST Request formWlanMultipleAP buffer overflow — A702R 8.8 High 2025-07-25
CVE-2025-8139 TOTOLINK A702R HTTP POST Request formPortFw buffer overflow — A702R 8.8 High 2025-07-25
CVE-2025-8138 TOTOLINK A702R HTTP POST Request formOneKeyAccessButton buffer overflow — A702R 8.8 High 2025-07-25
CVE-2025-8137 TOTOLINK A702R HTTP POST Request formIpQoS buffer overflow — A702R 8.8 High 2025-07-25
CVE-2025-8136 TOTOLINK A702R HTTP POST Request formFilter buffer overflow — A702R 8.8 High 2025-07-25
CVE-2025-8019 Shenzhen Libituo Technology LBT-T300-T310 appy.cgi sub_40B6F0 buffer overflow — LBT-T300-T310 8.8 High 2025-07-22
CVE-2025-7945 D-Link DIR-513 formSetWanDhcpplus buffer overflow — DIR-513 8.8 High 2025-07-21
CVE-2025-7914 Tenda AC6 httpd setparentcontrolinfo buffer overflow — AC6 8.8 High 2025-07-21
CVE-2025-7913 TOTOLINK T6 MQTT Service updateWifiInfo buffer overflow — T6 8.8 High 2025-07-20
CVE-2025-7912 TOTOLINK T6 MQTT Service recvSlaveUpgstatus buffer overflow — T6 8.8 High 2025-07-20
CVE-2025-7837 TOTOLINK T6 MQTT Service recvSlaveStaInfo buffer overflow — T6 8.8 High 2025-07-19
CVE-2025-53888 RIOT-OS has an ineffective size check that can lead to buffer overflow in link layer address filter /sys/net/link_layer/l2filter/l2filter.c — RIOT 9.8 - 2025-07-18
CVE-2025-7758 TOTOLINK T6 HTTP POST Request cstecgi.cgi setDiagnosisCfg buffer overflow — T6 8.8 High 2025-07-17
CVE-2025-7747 Tenda FH451 POST Request WizardHandle fromWizardHandle buffer overflow — FH451 8.8 High 2025-07-17
CVE-2025-34128 X360 VideoPlayer ActiveX Control Buffer Overflow via ConvertFile() — X360 VideoPlayer ActiveX Control 9.8AI Critical AI 2025-07-16
CVE-2025-7673 Zyxel VMG8825-T50K 安全漏洞 — VMG8825-T50K firmware 9.8 Critical 2025-07-16
CVE-2025-7571 UTT HiPER 840G aspApBasicConfigUrcp buffer overflow — HiPER 840G 8.8 High 2025-07-14
CVE-2025-7570 UTT HiPER 840G aspRemoteApConfTempSend buffer overflow — HiPER 840G 8.8 High 2025-07-14
CVE-2025-7468 Tenda FH1201 HTTP POST Request fromSafeUrlFilter buffer overflow — FH1201 8.8 High 2025-07-12
CVE-2025-7465 Tenda FH1201 HTTP POST Request fromRouteStatic buffer overflow — FH1201 8.8 High 2025-07-12

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