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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1808 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-5637 PCMan FTP Server SYSTEM Command buffer overflow — FTP Server 7.3 High2025-06-05
CVE-2025-5636 PCMan FTP Server SET Command buffer overflow — FTP Server 7.3 High2025-06-05
CVE-2025-5635 PCMan FTP Server PLS Command buffer overflow — FTP Server 7.3 High2025-06-05
CVE-2025-5634 PCMan FTP Server NOOP Command buffer overflow — FTP Server 7.3 High2025-06-05
CVE-2025-5629 Tenda AC10 HTTP SetPptpServerCfg formSetPPTPServer buffer overflow — AC10 8.8 High2025-06-05
CVE-2025-5609 Tenda AC18 AdvSetLanip fromadvsetlanip buffer overflow — AC18 8.8 High2025-06-04
CVE-2025-5608 Tenda AC18 SetSysAutoRebbotCfg formsetreboottimer buffer overflow — AC18 8.8 High2025-06-04
CVE-2025-5607 Tenda AC18 setPptpUserList formSetPPTPUserList buffer overflow — AC18 8.8 High2025-06-04
CVE-2025-5596 FreeFloat FTP Server REGET Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5595 FreeFloat FTP Server PROGRESS Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5594 FreeFloat FTP Server SET Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5593 FreeFloat FTP Server HOST Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5592 FreeFloat FTP Server PASSIVE Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5601 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in Wireshark — Wireshark 7.8 High2025-06-04
CVE-2025-5551 FreeFloat FTP Server SYSTEM Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5550 FreeFloat FTP Server PBSZ Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5549 FreeFloat FTP Server PASV Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5548 FreeFloat FTP Server NOOP Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2025-5547 FreeFloat FTP Server CDUP Command buffer overflow — FTP Server 7.3 High2025-06-04
CVE-2024-53013 Buffer Copy Without Checking Size of Input in Audio — Snapdragon 6.6 Medium2025-06-03
CVE-2025-5408 WAVLINK WL-WN576K1 HTTP POST Request login.cgi sys_login buffer overflow — QUANTUM D2G 9.8 Critical2025-06-01
CVE-2025-5357 FreeFloat FTP Server PWD Command buffer overflow — FTP Server 7.3 High2025-05-30
CVE-2025-5356 FreeFloat FTP Server BYE Command buffer overflow — FTP Server 7.3 High2025-05-30
CVE-2025-5331 PCMan FTP Server NLST Command buffer overflow — FTP Server 7.3 High2025-05-29
CVE-2025-5330 FreeFloat FTP Server RETR Command buffer overflow — FTP Server 7.3 High2025-05-29
CVE-2025-5295 FreeFloat FTP Server PORT Command buffer overflow — FTP Server 7.3 High2025-05-28
CVE-2025-5222 Icu: stack buffer overflow in the srbroot::addtag function 7.0 High2025-05-27
CVE-2025-5221 FreeFloat FTP Server QUOTE Command buffer overflow — FTP Server 7.3 High2025-05-27
CVE-2025-5220 FreeFloat FTP Server GET Command buffer overflow — FTP Server 7.3 High2025-05-27
CVE-2025-5219 FreeFloat FTP Server ASCII Command buffer overflow — FTP Server 7.3 High2025-05-27

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