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-10886 MODEL File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2023-53874 GOM Player 2.3.90.5360 Buffer Overflow via Equalizer Preset Name — GOM Player 5.5AIMediumAI2025-12-15
CVE-2025-59947 NanoMQ has Buffer Overflow — nanomq 9.8AICriticalAI2025-12-15
CVE-2025-14709 Shiguangwu sgwbox N3 WIRELESSCFGGET http_eshell_server buffer overflow — sgwbox N3 9.8 Critical2025-12-15
CVE-2025-14708 Shiguangwu sgwbox N3 WIREDCFGGET http_eshell_server buffer overflow — sgwbox N3 9.8 Critical2025-12-15
CVE-2025-14656 Tenda AC20 openSchedWifi httpd buffer overflow — AC20 8.8 High2025-12-14
CVE-2025-14535 UTT 进取 512W formConfigFastDirectionW strcpy buffer overflow — 进取 512W 9.8 Critical2025-12-11
CVE-2025-14534 UTT 进取 512W Endpoint formNatStaticMap strcpy buffer overflow — 进取 512W 9.8 Critical2025-12-11
CVE-2025-14526 Tenda CH22 L7Im frmL7ImForm buffer overflow — CH22 8.8 High2025-12-11
CVE-2025-14310 RethinkDB 安全漏洞 — rethinkdb 9.8AICriticalAI2025-12-09
CVE-2025-14196 H3C Magic B1 aspForm sub_44de0 buffer overflow — Magic B1 8.8 High2025-12-07
CVE-2025-14191 UTT 进取 512W formP2PLimitConfig strcpy buffer overflow — 进取 512W 8.8 High2025-12-07
CVE-2025-14187 UGREEN DH2100+ nas_svr create handler_file_backup_create buffer overflow — DH2100+ 7.2 High2025-12-07
CVE-2025-14141 UTT 进取 520W formArpBindConfig strcpy buffer overflow — 进取 520W 8.8 High2025-12-06
CVE-2025-14140 UTT 进取 520W websHostFilter strcpy buffer overflow — 进取 520W 6.5 Medium2025-12-06
CVE-2025-14139 UTT 进取 520W formConfigDnsFilterGlobal strcpy buffer overflow — 进取 520W 5.7 Medium2025-12-06
CVE-2025-14015 H3C Magic B0 aspForm EditWlanMacList buffer overflow — Magic B0 8.8 High2025-12-04
CVE-2025-66287 Webkitgtk: processing maliciously crafted web content may lead to an unexpected process crash — WebKitGTK 8.8 High2025-12-04
CVE-2025-11780 Stack-based buffer overflow vulnreability in Circutor SGE-PLC1000/SGE-PLC50 — Circutor 9.8AICriticalAI2025-12-02
CVE-2025-9557 Bluetooth: Mesh: Out-of-Bound Write in gen_prov_cont — Zephyr 7.6 High2025-11-26
CVE-2025-9558 Bluetooth: Mesh: Out-of-Bound Write in gen_prov_start — Zephyr 7.6 High2025-11-26
CVE-2025-13553 D-Link DWR-M920 formPinManageSetup sub_41C7FC buffer overflow — DWR-M920 8.8 High2025-11-23
CVE-2025-13552 D-Link DIR-822K/DWR-M920 formWlEncrypt buffer overflow — DIR-822K 8.8 High2025-11-23
CVE-2025-13551 D-Link DIR-822K/DWR-M920 formWanConfigSetup buffer overflow — DIR-822K 8.8 High2025-11-23
CVE-2025-13550 D-Link DIR-822K/DWR-M920 formVpnConfigSetup buffer overflow — DIR-822K 8.8 High2025-11-23
CVE-2025-13549 D-Link DIR-822K formNtp sub_455524 buffer overflow — DIR-822K 8.8 High2025-11-23
CVE-2025-13548 D-Link DIR-822K/DWR-M920 formFirewallAdv buffer overflow — DIR-822K 8.8 High2025-11-23
CVE-2025-65102 PJSIP is vulnerable to buffer overflow in Opus PLC — pjproject 6.5 -2025-11-21
CVE-2025-13400 Tenda CH22 WrlExtraGet formWrlExtraGet buffer overflow — CH22 8.8 High2025-11-19
CVE-2025-46776 Fortinet FortiExtender 安全漏洞 — FortiExtender 6.3 Medium2025-11-18

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