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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1811 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-4452 D-Link DIR-619L formSetWizard2 buffer overflow — DIR-619L 8.8 High2025-05-09
CVE-2025-4451 D-Link DIR-619L formSetWAN_Wizard52 buffer overflow — DIR-619L 8.8 High2025-05-09
CVE-2025-4450 D-Link DIR-619L formSetEasy_Wizard buffer overflow — DIR-619L 8.8 High2025-05-09
CVE-2025-4449 D-Link DIR-619L formEasySetupWizard3 buffer overflow — DIR-619L 8.8 High2025-05-09
CVE-2025-4448 D-Link DIR-619L formEasySetupWizard buffer overflow — DIR-619L 8.8 High2025-05-09
CVE-2025-4446 H3C GR-5400AX aspForm Edit_List_SSID buffer overflow — GR-5400AX 8.0 High2025-05-09
CVE-2025-4442 D-Link DIR-605L formSetWAN_Wizard55 buffer overflow — DIR-605L 8.8 High2025-05-08
CVE-2025-4441 D-Link DIR-605L formSetWAN_Wizard534 buffer overflow — DIR-605L 8.8 High2025-05-08
CVE-2025-4440 H3C GR-1800AX aspForm EnableIpv6 buffer overflow — GR-1800AX 8.0 High2025-05-08
CVE-2025-1253 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), Stack-based Buffer Overflow vulnerability in RTI Connext Professional (Core Libraries) allows Overflow Variables and Tags. — Connext Professional 9.1AICriticalAI2025-05-08
CVE-2025-36525 BIG-IP APM PingAccess Virtual Server Vulnerability — BIG-IP 7.5 High2025-05-07
CVE-2025-36557 BIG-IP HTTP vulnerability — BIG-IP 7.5 High2025-05-07
CVE-2025-4368 Tenda AC8 MtuSetMacWan formGetRouterStatus buffer overflow — AC8 8.8 High2025-05-06
CVE-2025-4348 D-Link DIR-600L formSetWanL2TP buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2025-4347 D-Link DIR-600L formWlSiteSurvey buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2025-4346 D-Link DIR-600L formSetWAN_Wizard534 buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2025-4345 D-Link DIR-600L formSetLog buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2025-4344 D-Link DIR-600L formLogin buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2025-25052 arkcompiler_ets_runtime has a buffer overflow vulnerability — OpenHarmony 3.3 Low2025-05-06
CVE-2025-4343 D-Link DIR-600L formEasySetupWizard buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2024-49830 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Audio — Snapdragon 6.6 Medium2025-05-06
CVE-2024-49829 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Camera — Snapdragon 6.7 Medium2025-05-06
CVE-2025-4342 D-Link DIR-600L formEasySetupWizard3 buffer overflow — DIR-600L 8.8 High2025-05-06
CVE-2025-4299 Tenda AC1206 openSchedWifi setSchedWifi buffer overflow — AC1206 8.8 High2025-05-06
CVE-2025-4298 Tenda AC1206 setcfm formSetCfm buffer overflow — AC1206 8.8 High2025-05-05
CVE-2025-4290 PCMan FTP Server SMNT Command buffer overflow — FTP Server 7.3 High2025-05-05
CVE-2025-4289 PCMan FTP Server RNTO Command buffer overflow — FTP Server 7.3 High2025-05-05
CVE-2025-4288 PCMan FTP Server RNFR Command buffer overflow — FTP Server 7.3 High2025-05-05
CVE-2025-4255 PCMan FTP Server RMD Command buffer overflow — FTP Server 7.3 High2025-05-05
CVE-2025-4254 PCMan FTP Server LIST Command buffer overflow — FTP Server 7.3 High2025-05-04

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