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-5551 FreeFloat FTP Server SYSTEM Command buffer overflow — FTP Server 7.3 High 2025-06-04
CVE-2025-5550 FreeFloat FTP Server PBSZ Command buffer overflow — FTP Server 7.3 High 2025-06-04
CVE-2025-5549 FreeFloat FTP Server PASV Command buffer overflow — FTP Server 7.3 High 2025-06-04
CVE-2025-5548 FreeFloat FTP Server NOOP Command buffer overflow — FTP Server 7.3 High 2025-06-04
CVE-2025-5547 FreeFloat FTP Server CDUP Command buffer overflow — FTP Server 7.3 High 2025-06-04
CVE-2024-53013 Buffer Copy Without Checking Size of Input in Audio — Snapdragon 6.6 Medium 2025-06-03
CVE-2025-5408 WAVLINK WL-WN576K1 HTTP POST Request login.cgi sys_login buffer overflow — QUANTUM D2G 9.8 Critical 2025-06-01
CVE-2025-5357 FreeFloat FTP Server PWD Command buffer overflow — FTP Server 7.3 High 2025-05-30
CVE-2025-5356 FreeFloat FTP Server BYE Command buffer overflow — FTP Server 7.3 High 2025-05-30
CVE-2025-5331 PCMan FTP Server NLST Command buffer overflow — FTP Server 7.3 High 2025-05-29
CVE-2025-5330 FreeFloat FTP Server RETR Command buffer overflow — FTP Server 7.3 High 2025-05-29
CVE-2025-5295 FreeFloat FTP Server PORT Command buffer overflow — FTP Server 7.3 High 2025-05-28
CVE-2025-5222 Icu: stack buffer overflow in the srbroot::addtag function 7.0 High 2025-05-27
CVE-2025-5221 FreeFloat FTP Server QUOTE Command buffer overflow — FTP Server 7.3 High 2025-05-27
CVE-2025-5220 FreeFloat FTP Server GET Command buffer overflow — FTP Server 7.3 High 2025-05-27
CVE-2025-5219 FreeFloat FTP Server ASCII Command buffer overflow — FTP Server 7.3 High 2025-05-27
CVE-2025-5218 FreeFloat FTP Server LITERAL Command buffer overflow — FTP Server 7.3 High 2025-05-27
CVE-2025-5217 FreeFloat FTP Server RMDIR Command buffer overflow — FTP Server 7.3 High 2025-05-27
CVE-2025-5156 H3C GR-5400AX aspForm EditWlanMacList buffer overflow — GR-5400AX 8.8 High 2025-05-25
CVE-2025-5112 FreeFloat FTP Server MGET Command buffer overflow — FTP Server 7.3 High 2025-05-23
CVE-2025-5111 FreeFloat FTP Server TYPE Command buffer overflow — FTP Server 7.3 High 2025-05-23
CVE-2025-5110 FreeFloat FTP Server VERBOSE Command buffer overflow — FTP Server 7.3 High 2025-05-23
CVE-2025-5109 FreeFloat FTP Server STATUS Command buffer overflow — FTP Server 7.3 High 2025-05-23
CVE-2025-5076 FreeFloat FTP Server SEND Command buffer overflow — FTP Server 7.3 High 2025-05-22
CVE-2025-5075 FreeFloat FTP Server DEBUG Command buffer overflow — FTP Server 7.3 High 2025-05-22
CVE-2025-46714 Sandboxie has Pool Buffer Overflow in SbieDrv.sys API (API_GET_SECURE_PARAM) — Sandboxie 7.8 High 2025-05-22
CVE-2025-46713 Sandboxie has Pool Buffer Overflow in SbieDrv.sys API (API_SET_SECURE_PARAM) — Sandboxie 7.8 High 2025-05-22
CVE-2025-5074 FreeFloat FTP Server PROMPT Command buffer overflow — FTP Server 7.3 High 2025-05-22
CVE-2025-5073 FreeFloat FTP Server MKDIR Command buffer overflow — FTP Server 7.3 High 2025-05-22
CVE-2025-5053 FreeFloat FTP Server MDIR Command buffer overflow — FTP Server 7.3 High 2025-05-21

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