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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1767 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-2025-6129 TOTOLINK EX1200T HTTP POST Request formSaveConfig buffer overflow — EX1200T 8.8 High2025-06-16
CVE-2025-6128 TOTOLINK EX1200T HTTP POST Request formWirelessTbl buffer overflow — EX1200T 8.8 High2025-06-16
CVE-2025-6113 Tenda FH1203 AdvSetLanip fromadvsetlanip buffer overflow — FH1203 8.8 High2025-06-16
CVE-2025-6112 Tenda FH1205 AdvSetLanip fromadvsetlanip buffer overflow — FH1205 8.8 High2025-06-16
CVE-2025-6098 UTT 进取 750W API setSysAdm strcpy buffer overflow — 进取 750W 9.8 Critical2025-06-16
CVE-2025-6091 H3C GR-3000AX aspForm UpdateIpv6Params buffer overflow — GR-3000AX 8.8 High2025-06-15
CVE-2025-6090 H3C GR-5400AX aspForm UpdateIpv6params buffer overflow — GR-5400AX 8.8 High2025-06-15
CVE-2025-5911 TOTOLINK EX1200T HTTP POST Request formDMZ buffer overflow — EX1200T 8.8 High2025-06-10
CVE-2025-5910 TOTOLINK EX1200T HTTP POST Request formWsc buffer overflow — EX1200T 8.8 High2025-06-10
CVE-2025-5909 TOTOLINK EX1200T HTTP POST Request formReflashClientTbl buffer overflow — EX1200T 8.8 High2025-06-10
CVE-2025-5908 TOTOLINK EX1200T HTTP POST Request formIpQoS buffer overflow — EX1200T 8.8 High2025-06-10
CVE-2025-5907 TOTOLINK EX1200T HTTP POST Request formFilter buffer overflow — EX1200T 8.8 High2025-06-10
CVE-2025-5905 TOTOLINK T10 POST Request cstecgi.cgi setWiFiRepeaterCfg buffer overflow — T10 8.8 High2025-06-10
CVE-2025-5904 TOTOLINK T10 POST Request cstecgi.cgi setWiFiMeshName buffer overflow — T10 8.8 High2025-06-10
CVE-2025-5903 TOTOLINK T10 POST Request cstecgi.cgi setWiFiAclRules buffer overflow — T10 8.8 High2025-06-09
CVE-2025-5902 TOTOLINK T10 POST Request cstecgi.cgi setUpgradeFW buffer overflow — T10 8.8 High2025-06-09
CVE-2025-5901 TOTOLINK T10 POST Request cstecgi.cgi UploadCustomModule buffer overflow — T10 8.8 High2025-06-09
CVE-2025-5875 TP-LINK Technologies TL-IPC544EP-W4 main sub_69064 buffer overflow — TL-IPC544EP-W4 8.8 High2025-06-09
CVE-2025-5862 Tenda AC7 setPptpUserList formSetPPTPUserList buffer overflow — AC7 8.8 High2025-06-09
CVE-2025-5861 Tenda AC7 AdvSetLanip fromadvsetlanip buffer overflow — AC7 8.8 High2025-06-09
CVE-2025-5854 Tenda AC6 AdvSetLanip fromadvsetlanip buffer overflow — AC6 8.8 High2025-06-09
CVE-2025-5852 Tenda AC6 setPptpUserList formSetPPTPUserList buffer overflow — AC6 8.8 High2025-06-09
CVE-2025-5851 Tenda AC15 HTTP POST Request AdvSetLanip fromadvsetlanip buffer overflow — AC15 8.8 High2025-06-08
CVE-2025-5850 Tenda AC15 HTTP POST Request SetLEDCf formsetschedled buffer overflow — AC15 8.8 High2025-06-08
CVE-2025-5848 Tenda AC15 HTTP POST Request setPptpUserList formSetPPTPUserList buffer overflow — AC15 8.8 High2025-06-08
CVE-2025-5839 Tenda AC9 POST Request AdvSetLanip fromadvsetlanip buffer overflow — AC9 8.8 High2025-06-07
CVE-2025-5795 Tenda AC5 AdvSetLanip fromadvsetlanip buffer overflow — AC5 8.8 High2025-06-06
CVE-2025-5794 Tenda AC5 setPptpUserList formSetPPTPUserList buffer overflow — AC5 8.8 High2025-06-06
CVE-2025-5793 TOTOLINK EX1200T HTTP POST Request formPortFw buffer overflow — EX1200T 8.8 High2025-06-06
CVE-2025-5792 TOTOLINK EX1200T HTTP POST Request formWlanRedirect buffer overflow — EX1200T 8.8 High2025-06-06

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