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-3854 H3C GR-3000AX HTTP POST Request aspForm Edit_List_SSID buffer overflow — GR-3000AX 8.0 High2025-04-22
CVE-2025-3845 markparticle WebServer buffer.cpp HasWritten buffer overflow — WebServer 7.3 High2025-04-21
CVE-2025-3786 Tenda AC15 WifiExtraSet fromSetWirelessRepeat buffer overflow — AC15 8.8 High2025-04-18
CVE-2025-3763 SourceCodester Phone Management System Password main buffer overflow — Phone Management System 5.3 Medium2025-04-17
CVE-2025-3762 PCMan FTP Server MPUT Command buffer overflow — FTP Server 7.3 High2025-04-17
CVE-2025-3728 SourceCodester Simple Hotel Booking System login buffer overflow — Simple Hotel Booking System 5.3 Medium2025-04-16
CVE-2025-3727 PCMan FTP Server STATUS Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3726 PCMan FTP Server CD Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3725 PCMan FTP Server MIC Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3724 PCMan FTP Server DIR Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3723 PCMan FTP Server MDTM Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3683 PCMan FTP Server SIZE Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3682 PCMan FTP Server PASV Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3681 PCMan FTP Server MODE Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3680 PCMan FTP Server LANG Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3679 PCMan FTP Server HOST Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-3678 PCMan FTP Server HELP Command buffer overflow — FTP Server 7.3 High2025-04-16
CVE-2025-1277 PDF File Parsing Memory Corruption Vulnerability — Revit 7.8 High2025-04-15
CVE-2025-3380 PCMan FTP Server FEAT Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3379 PCMan FTP Server EPSV Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3378 PCMan FTP Server EPRT Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3377 PCMan FTP Server ENC Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3376 PCMan FTP Server CONF Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3375 PCMan FTP Server CDUP Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3374 PCMan FTP Server CCC Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3373 PCMan FTP Server SITE CHMOD Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3372 PCMan FTP Server MKDIR Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3371 PCMan FTP Server DELETE Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-3349 PCMan FTP Server SYST Command buffer overflow — FTP Server 7.3 High2025-04-07
CVE-2025-21443 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Automotive Vehicle Networks — Snapdragon 7.8 High2025-04-07

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