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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1912 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-2018-25293 Prime95 29.4b7 Denial of Service via Proxy Password Field — Prime95 6.2 Medium 2026-04-26
CVE-2018-25292 Bome Restorator 1793 Denial of Service via Buffer Overflow — Restorator 6.2 Medium 2026-04-26
CVE-2018-25291 Project64 2.3.2 Denial of Service via Plugin Directory — Project64 6.2 Medium 2026-04-26
CVE-2018-25290 Easyboot 6.6.0 Buffer Overflow Denial of Service — Easyboot 6.2 Medium 2026-04-26
CVE-2018-25289 Softdisk 3.0.3 Buffer Overflow Denial of Service — Softdisk 6.2 Medium 2026-04-26
CVE-2018-25288 StyleWriter 1.0 Denial of Service via Pattern Input — StyleWriter 6.2 Medium 2026-04-26
CVE-2018-25287 Drive Power Manager 1.10 Denial of Service via Name Field — Drive Power Manager 5.5 Medium 2026-04-26
CVE-2018-25286 Easy PhotoResQ 1.0 Buffer Overflow Denial of Service — Easy PhotoResQ 6.2 Medium 2026-04-26
CVE-2018-25285 Fathom 2.4 Denial of Service via Authorization Code Buffer Overflow — Fathom 5.5 Medium 2026-04-26
CVE-2018-25284 HD Tune Pro 5.70 Denial of Service via Options Dialog — HD Tune Pro 6.2 Medium 2026-04-26
CVE-2018-25283 iSmartViewPro 1.5 Buffer Overflow via SavePath Parameter — iSmartViewPro 8.4 High 2026-04-26
CVE-2018-25281 iCash 7.6.5 Denial of Service via Connect to Server — iCash 5.5 Medium 2026-04-26
CVE-2018-25280 Infiltrator Network Security Scanner 4.6 Denial of Service — Infiltrator Network Security Scanner 5.5 Medium 2026-04-26
CVE-2018-25277 PixGPS 1.1.8 Buffer Overflow Denial of Service — PixGPS 6.2 Medium 2026-04-26
CVE-2018-25278 PicaJet FX 2.6.5 Denial of Service via Registration Fields — PicaJet FX 6.2 Medium 2026-04-26
CVE-2018-25276 RoboImport 1.2.0.72 Denial of Service via Registration Fields — RoboImport 5.5 Medium 2026-04-26
CVE-2018-25275 Faleemi Plus 1.0.2 Denial of Service via Buffer Overflow — Faleemi Plus 6.2 Medium 2026-04-26
CVE-2018-25273 CrossFont 7.5 Denial of Service via License Key Field — CrossFont 6.2 Medium 2026-04-26
CVE-2018-25264 TransMac 12.2 Denial of Service via License Key Field — TransMac 6.2 Medium 2026-04-26
CVE-2018-25263 Faleemi Desktop Software 1.8.2 Local Buffer Overflow SEH — Faleemi Desktop Software 8.4 High 2026-04-26
CVE-2026-7033 Tenda F456 SafeClientFilter fromSafeClientFilter buffer overflow — F456 8.8 High 2026-04-26
CVE-2026-7032 Tenda F456 SafeEmailFilter buffer overflow — F456 8.8 High 2026-04-26
CVE-2026-7031 Tenda F456 SafeMacFilter fromSafeMacFilter buffer overflow — F456 8.8 High 2026-04-26
CVE-2026-7030 Tenda F456 RouteStatic fromRouteStatic buffer overflow — F456 8.8 High 2026-04-26
CVE-2026-7029 Tenda F456 addressNat fromaddressNat buffer overflow — F456 8.8 High 2026-04-26
CVE-2026-7019 Tenda F456 P2pListFilter fromP2pListFilter buffer overflow — F456 8.8 High 2026-04-26
CVE-2026-6988 Tenda HG10 Boa Service formRouting formRoute buffer overflow — HG10 8.8 High 2026-04-25
CVE-2026-41476 Deskflow: clipboard deserialization global-buffer-overflow — deskflow 9.1AI Critical AI 2026-04-24
CVE-2026-6632 Tenda F451 httpd SafeClientFilter fromSafeClientFilter buffer overflow — F451 8.8 High 2026-04-20
CVE-2026-6631 Tenda F451 httpd webExcptypemanFilter fromwebExcptypemanFilter buffer overflow — F451 8.8 High 2026-04-20

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