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-4161 PCMan FTP Server VERBOSE Command buffer overflow — FTP Server 7.3 High2025-05-01
CVE-2025-4160 PCMan FTP Server LS Command buffer overflow — FTP Server 7.3 High2025-05-01
CVE-2025-4159 PCMan FTP Server GLOB Command buffer overflow — FTP Server 7.3 High2025-05-01
CVE-2025-4158 PCMan FTP Server PROMPT Command buffer overflow — FTP Server 7.3 High2025-05-01
CVE-2025-4150 Netgear EX6200 sub_54340 buffer overflow — EX6200 8.8 High2025-05-01
CVE-2025-4149 Netgear EX6200 sub_54014 buffer overflow — EX6200 8.8 High2025-05-01
CVE-2025-4148 Netgear EX6200 sub_503FC buffer overflow — EX6200 8.8 High2025-05-01
CVE-2025-4147 Netgear EX6200 sub_47F7C buffer overflow — EX6200 8.8 High2025-05-01
CVE-2025-4146 Netgear EX6200 sub_41940 buffer overflow — EX6200 8.8 High2025-05-01
CVE-2025-4145 Netgear EX6200 sub_3D0BC buffer overflow — EX6200 8.8 High2025-05-01
CVE-2025-4142 Netgear EX6200 sub_3C8EC buffer overflow — EX6200 8.8 High2025-04-30
CVE-2025-4141 Netgear EX6200 sub_3C03C buffer overflow — EX6200 8.8 High2025-04-30
CVE-2025-4140 Netgear EX6120 sub_30394 buffer overflow — EX6120 8.8 High2025-04-30
CVE-2025-4139 Netgear EX6120 fwAcosCgiInbound buffer overflow — EX6120 8.8 High2025-04-30
CVE-2025-4120 Netgear JWNR2000v2 sub_4238E8 buffer overflow — JWNR2000v2 8.8 High2025-04-30
CVE-2025-4117 Netgear JWNR2000v2 sub_41A914 buffer overflow — JWNR2000v2 5.5 Medium2025-04-30
CVE-2025-4116 Netgear JWNR2000v2 get_cur_lang_ver buffer overflow — JWNR2000v2 8.8 High2025-04-30
CVE-2025-4115 Netgear JWNR2000v2 default_version_is_new buffer overflow — JWNR2000v2 8.8 High2025-04-30
CVE-2025-4114 Netgear JWNR2000v2 check_language_file buffer overflow — JWNR2000v2 8.8 High2025-04-30
CVE-2025-4079 PCMan FTP Server RENAME Command buffer overflow — FTP Server 7.3 High2025-04-29
CVE-2025-3993 TOTOLINK N150RT formWsc buffer overflow — N150RT 8.8 High2025-04-28
CVE-2025-3992 TOTOLINK N150RT formWlwds buffer overflow — N150RT 8.8 High2025-04-28
CVE-2025-3991 TOTOLINK N150RT formWdsEncrypt buffer overflow — N150RT 8.8 High2025-04-27
CVE-2025-3990 TOTOLINK N150RT formVlan buffer overflow — N150RT 8.8 High2025-04-27
CVE-2025-3989 TOTOLINK N150RT formStaticDHCP buffer overflow — N150RT 8.8 High2025-04-27
CVE-2025-3988 TOTOLINK N150RT formPortFw buffer overflow — N150RT 8.8 High2025-04-27
CVE-2025-2851 GL.iNet GL-A1300 Slate Plus RPC plugins.so buffer overflow — GL-A1300 Slate Plus 8.0 High2025-04-26
CVE-2024-6199 Unauthenticated Remote Code Execution — RM5110 7.5 -2025-04-25
CVE-2024-6198 SNORE Interface Unauthenticated Remote Code Execution — RM4100 8.8 -2025-04-25
CVE-2025-46397 Xfig: xfig: stack-overflow allows possible code execution via local input manipulation 7.8 High2025-04-23

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