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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1810 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-4846 FreeFloat FTP Server MPUT Command buffer overflow — FTP Server 7.3 High2025-05-18
CVE-2025-4845 FreeFloat FTP Server TRACE Command buffer overflow — FTP Server 7.3 High2025-05-18
CVE-2025-4844 FreeFloat FTP Server CD Command buffer overflow — FTP Server 7.3 High2025-05-18
CVE-2025-4835 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formWlanRedirect buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4834 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formSetLg buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4833 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formNtp buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4832 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formDosCfg buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4831 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formSiteSurveyProfile buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4830 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formSysCmd buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4829 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formStats sub_40BE30 buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4827 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formSaveConfig buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4826 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formWirelessTbl buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4825 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formDMZ buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4824 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formWsc buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4823 TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formReflashClientTbl submit-url buffer overflow — A702R 8.8 High2025-05-17
CVE-2025-4792 FreeFloat FTP Server MDELETE Command buffer overflow — FTP Server 7.3 High2025-05-16
CVE-2025-4791 FreeFloat FTP Server HASH Command buffer overflow — FTP Server 7.3 High2025-05-16
CVE-2025-4790 FreeFloat FTP Server GLOB Command buffer overflow — FTP Server 7.3 High2025-05-16
CVE-2025-4789 FreeFloat FTP Server LCD Command buffer overflow — FTP Server 7.3 High2025-05-16
CVE-2025-4788 FreeFloat FTP Server DELETE Command buffer overflow — FTP Server 7.3 High2025-05-16
CVE-2025-4733 TOTOLINK A3002R/A3002RU HTTP POST Request formIpQoS buffer overflow — A3002R 8.8 High2025-05-16
CVE-2025-4732 TOTOLINK A3002R/A3002RU HTTP POST Request formFilter buffer overflow — A3002R 8.8 High2025-05-16
CVE-2025-4731 TOTOLINK A3002R/A3002RU HTTP POST Request formPortFw buffer overflow — A3002R 8.8 High2025-05-16
CVE-2025-4730 TOTOLINK A3002R/A3002RU HTTP POST Request formMapDel buffer overflow — A3002R 8.8 High2025-05-16
CVE-2025-46785 Zoom Workplace Apps for Windows - Buffer Over-read — Zoom Workplace Apps 6.5 Medium2025-05-14
CVE-2025-3496 AUMA Riester: Buffer overflow in service telegram — AC1.2 7.5 High2025-05-12
CVE-2025-4497 code-projects Simple Banking System Sign In buffer overflow — Simple Banking System 5.3 Medium2025-05-10
CVE-2025-4496 TOTOLINK T10/A3100R/A950RG/A800R/N600R/A3000RU/A810R cstecgi.cgi CloudACMunualUpdate buffer overflow — T10 8.8 High2025-05-10
CVE-2025-4462 TOTOLINK N150RT formWsc buffer overflow — N150RT 8.8 High2025-05-09
CVE-2025-4452 D-Link DIR-619L formSetWizard2 buffer overflow — DIR-619L 8.8 High2025-05-09

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