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-15460 UTT 进取 520W formPptpClientConfig strcpy buffer overflow — 进取 520W 8.8 High 2026-01-05
CVE-2025-15459 UTT 进取 520W formUser strcpy buffer overflow — 进取 520W 8.8 High 2026-01-05
CVE-2025-48721 QTS, QuTS hero — QTS 6.5 - 2026-01-02
CVE-2025-52872 QTS, QuTS hero — QTS 8.1 - 2026-01-02
CVE-2025-52864 QTS, QuTS hero — QTS 8.1 - 2026-01-02
CVE-2025-52863 QTS, QuTS hero — QTS 8.1 - 2026-01-02
CVE-2025-15431 UTT 进取 512W formFtpServerDirConfig strcpy buffer overflow — 进取 512W 8.8 High 2026-01-02
CVE-2025-15430 UTT 进取 512W formFtpServerShareDirSelcet strcpy buffer overflow — 进取 512W 8.8 High 2026-01-02
CVE-2025-15429 UTT 进取 512W formConfigCliForEngineerOnly strcpy buffer overflow — 进取 512W 8.8 High 2026-01-02
CVE-2025-15428 UTT 进取 512W formRemoteControl strcpy buffer overflow — 进取 512W 8.8 High 2026-01-02
CVE-2025-15356 Tenda AC20 PowerSaveSet sscanf buffer overflow — AC20 8.8 High 2025-12-30
CVE-2025-15218 Tenda AC10U POST Request Parameter AdvSetLanip fromadvsetlanip buffer overflow — AC10U 8.8 High 2025-12-30
CVE-2025-15217 Tenda AC23 HTTP POST Request formSetPPTPUserList buffer overflow — AC23 8.8 High 2025-12-30
CVE-2025-15215 Tenda AC10U HTTP POST Request setPptpUserList formSetPPTPUserList buffer overflow — AC10U 8.8 High 2025-12-30
CVE-2025-15193 D-Link DWR-M920 formParentControl sub_423848 buffer overflow — DWR-M920 8.8 High 2025-12-29
CVE-2025-15189 D-Link DWR-M920 formDefRoute sub_464794 buffer overflow — DWR-M920 8.8 High 2025-12-29
CVE-2025-15092 UTT 进取 512W ConfigExceptMSN strcpy buffer overflow — 进取 512W 8.8 High 2025-12-26
CVE-2025-15091 UTT 进取 512W formPictureUrl strcpy buffer overflow — 进取 512W 8.8 High 2025-12-25
CVE-2025-15090 UTT 进取 512W formConfigNoticeConfig strcpy buffer overflow — 进取 512W 8.8 High 2025-12-25
CVE-2025-15089 UTT 进取 512W APSecurity strcpy buffer overflow — 进取 512W 8.8 High 2025-12-25
CVE-2022-50689 Cobian Reflector 0.9.93 RC1 Local Denial of Service via Password Field — Cobian Reflector 6.2 Medium 2025-12-22
CVE-2022-50687 Cobian Backup 11 Gravity 11.2.0.582 Local Denial of Service via Password Field — Cobian Backup Gravity 5.5 Medium 2025-12-22
CVE-2025-47372 Buffer Copy Without Checking Size of Input in Boot — Snapdragon 9.0 Critical 2025-12-18
CVE-2025-47321 Buffer Copy Without Checking Size of Input in Core Services — Snapdragon 7.8 High 2025-12-18
CVE-2025-66647 RIOT OS has buffer overflow in gnrc_ipv6_ext_frag_reass — RIOT 7.2AI High AI 2025-12-17
CVE-2025-10889 CATPART File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High 2025-12-15
CVE-2025-10887 MODEL File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High 2025-12-15
CVE-2025-10886 MODEL File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High 2025-12-15
CVE-2023-53874 GOM Player 2.3.90.5360 Buffer Overflow via Equalizer Preset Name — GOM Player 5.5AI Medium AI 2025-12-15
CVE-2025-59947 NanoMQ has Buffer Overflow — nanomq 9.8AI Critical AI 2025-12-15

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