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-41418 TB-eye多款产品 安全漏洞 — XRN-410SN/TE 5.3 Medium2025-06-27
CVE-2025-6751 Linksys E8450 HTTP POST Request portal.cgi set_device_language buffer overflow — E8450 8.8 High2025-06-27
CVE-2025-6734 UTT HiPER 840G API formP2PLimitConfig sub_484E40 buffer overflow — HiPER 840G 8.8 High2025-06-26
CVE-2025-6733 UTT HiPER 840G API formConfigDnsFilterGlobal sub_416928 buffer overflow — HiPER 840G 8.8 High2025-06-26
CVE-2025-6732 UTT HiPER 840G API setSysAdm strcpy buffer overflow — HiPER 840G 8.8 High2025-06-26
CVE-2025-6627 TOTOLINK A702R HTTP POST Request formIpv6Setup buffer overflow — A702R 8.8 High2025-06-25
CVE-2025-5828 Autel MaxiCharger AC Wallbox Commercial wLength Buffer Overflow Remote Code Execution Vulnerability — Autel MaxiCharger AC Wallbox Commercial 6.8AIMediumAI2025-06-25
CVE-2025-6568 TOTOLINK EX1200T HTTP POST Request formIpv6Setup buffer overflow — EX1200T 8.8 High2025-06-24
CVE-2025-6402 TOTOLINK X15 HTTP POST Request formIpv6Setup buffer overflow — X15 8.8 High2025-06-21
CVE-2025-6400 TOTOLINK N300RH HTTP POST Message formPortFw buffer overflow — N300RH 8.8 High2025-06-21
CVE-2025-6399 TOTOLINK X15 HTTP POST Request formIPv6Addr buffer overflow — X15 8.8 High2025-06-21
CVE-2025-6393 TOTOLINK A702R/A3002R/A3002RU/EX1200T HTTP POST Request formIPv6Addr buffer overflow — A702R 8.8 High2025-06-21
CVE-2025-6337 TOTOLINK A3002R/A3002RU HTTP POST Request formTmultiAP buffer overflow — A3002R 8.8 High2025-06-20
CVE-2025-6336 TOTOLINK EX1200T HTTP POST Request formTmultiAP buffer overflow — EX1200T 8.8 High2025-06-20
CVE-2025-6165 TOTOLINK X15 HTTP POST Request formTmultiAP buffer overflow — X15 8.8 High2025-06-17
CVE-2025-6164 TOTOLINK A3002R HTTP POST Request formMultiAP buffer overflow — A3002R 8.8 High2025-06-17
CVE-2025-6163 TOTOLINK A3002RU HTTP POST Request formMultiAP buffer overflow — A3002RU 8.8 High2025-06-17
CVE-2025-6162 TOTOLINK EX1200T HTTP POST Request formMultiAP buffer overflow — EX1200T 8.8 High2025-06-17
CVE-2025-6151 TP-Link TL-WR940N, TL-WR841N WanSlaacCfgRpm.htm buffer overflow — TL-WR940N V4 9.8AICriticalAI2025-06-17
CVE-2025-6150 TOTOLINK X15 HTTP POST Request formMultiAP buffer overflow — X15 8.8 High2025-06-17
CVE-2025-6149 TOTOLINK A3002R HTTP POST Request formSysLog buffer overflow — A3002R 8.8 High2025-06-17
CVE-2025-6148 TOTOLINK A3002RU HTTP POST Request formSysLog buffer overflow — A3002RU 8.8 High2025-06-17
CVE-2025-6147 TOTOLINK A702R HTTP POST Request formSysLog buffer overflow — A702R 8.8 High2025-06-17
CVE-2025-6146 TOTOLINK X15 HTTP POST Request formSysLog buffer overflow — X15 8.8 High2025-06-16
CVE-2025-6145 TOTOLINK EX1200T HTTP POST Request formSysLog buffer overflow — EX1200T 8.8 High2025-06-16
CVE-2025-6144 TOTOLINK EX1200T HTTP POST Request formSysCmd buffer overflow — EX1200T 8.8 High2025-06-16
CVE-2025-6143 TOTOLINK EX1200T HTTP POST Request formNtp buffer overflow — EX1200T 8.8 High2025-06-16
CVE-2025-6138 TOTOLINK T10 HTTP POST Request cstecgi.cgi setWizardCfg buffer overflow — T10 8.8 High2025-06-16
CVE-2025-6137 TOTOLINK T10 HTTP POST Request cstecgi.cgi setWiFiScheduleCfg buffer overflow — T10 8.8 High2025-06-16
CVE-2025-6130 TOTOLINK EX1200T HTTP POST Request formStats buffer overflow — EX1200T 8.8 High2025-06-16

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