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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1914 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-2025-7463 Tenda FH1201 HTTP POST Request AdvSetWrlsafeset formWrlsafeset buffer overflow — FH1201 8.8 High 2025-07-12
CVE-2025-7460 TOTOLINK T6 HTTP POST Request cstecgi.cgi setWiFiAclRules buffer overflow — T6 8.8 High 2025-07-11
CVE-2025-49464 Zoom Clients for Windows- Classic Buffer Overflow — Zoom Clients for Windows 6.5 Medium 2025-07-10
CVE-2025-46789 Zoom Clients for Windows - Classic Buffer Overflow — Zoom Clients for Windows 6.5 Medium 2025-07-10
CVE-2025-5037 RFA File Parsing Memory Corruption Vulnerability — Revit 7.8 High 2025-07-10
CVE-2025-48386 Git allows a buffer overflow in 'wincred' credential helper — git 6.3 Medium 2025-07-08
CVE-2025-7345 Gdk‑pixbuf: heap‑buffer‑overflow in gdk‑pixbuf 7.5 High 2025-07-08
CVE-2025-27058 Buffer Copy Without Checking Size of Input in Computer Vision — Snapdragon 7.8 High 2025-07-08
CVE-2025-27052 Buffer Copy Without Checking Size of Input in Core Services — Snapdragon 7.8 High 2025-07-08
CVE-2025-27043 Buffer Copy Without Checking Size of Input in Video — Snapdragon 7.8 High 2025-07-08
CVE-2025-21445 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Data HLOS - QX — Snapdragon 7.8 High 2025-07-08
CVE-2025-21444 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Data HLOS - QX — Snapdragon 7.8 High 2025-07-08
CVE-2025-21426 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Camera_Linux — Snapdragon 6.6 Medium 2025-07-08
CVE-2025-24004 USB-C Buffer Overflow via Display Interface in EV Charging Stations — CHARX SEC-3150 5.2 Medium 2025-07-08
CVE-2025-24003 MQTT OOB Write Vulnerability in EichrechtAgents of German EV Charging Stations — CHARX SEC-3150 8.2 High 2025-07-08
CVE-2025-7118 UTT HiPER 840G formPictureUrl buffer overflow — HiPER 840G 8.8 High 2025-07-07
CVE-2025-7117 UTT HiPER 840G websWhiteList buffer overflow — HiPER 840G 8.8 High 2025-07-07
CVE-2025-7116 UTT 进取 750W Fast_wireless_conf buffer overflow — 进取 750W 8.8 High 2025-07-07
CVE-2025-7077 Shenzhen Libituo Technology LBT-T300-T310 appy.cgi config_3g_para buffer overflow — LBT-T300-T310 8.8 High 2025-07-06
CVE-2025-6953 TOTOLINK A3002RU HTTP POST Request formParentControl buffer overflow — A3002RU 8.8 High 2025-07-01
CVE-2025-6940 TOTOLINK A702R HTTP POST Request formParentControl buffer overflow — A702R 8.8 High 2025-07-01
CVE-2025-6939 TOTOLINK A3002RU HTTP POST Request formWlSiteSurvey buffer overflow — A3002RU 8.8 High 2025-07-01
CVE-2025-6882 D-Link DIR-513 formSetWanPPTP buffer overflow — DIR-513 8.8 High 2025-06-30
CVE-2025-6881 D-Link DI-8100 jhttpd pppoe_base.asp buffer overflow — DI-8100 8.8 High 2025-06-30
CVE-2025-6825 TOTOLINK A702R HTTP POST Request formWlSiteSurvey buffer overflow — A702R 8.8 High 2025-06-28
CVE-2025-6824 TOTOLINK X15 HTTP POST Request formParentControl buffer overflow — X15 8.8 High 2025-06-28
CVE-2023-28904 Bypass of secure boot process — Volkswagen MIB3 infotainment system MIB3 OI MQB 5.2 Medium 2025-06-28
CVE-2025-41418 TB-eye多款产品 安全漏洞 — XRN-410SN/TE 5.3 Medium 2025-06-27
CVE-2025-6751 Linksys E8450 HTTP POST Request portal.cgi set_device_language buffer overflow — E8450 8.8 High 2025-06-27
CVE-2025-6734 UTT HiPER 840G API formP2PLimitConfig sub_484E40 buffer overflow — HiPER 840G 8.8 High 2025-06-26

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