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-2010-10017 WM Downloader 3.1.2.2 Buffer Overflow via Malformed M3U File — WM Downloader 7.8 - 2025-08-30
CVE-2010-10016 BS.Player 2.57 Buffer Overflow via M3U Playlist Import — BS.Player Free and Pro Editions 7.1 - 2025-08-30
CVE-2025-30265 QTS, QuTS hero — QTS 8.1 - 2025-08-29
CVE-2025-9443 Tenda CH22 editUserName formeditUserName buffer overflow — CH22 8.8 High 2025-08-26
CVE-2025-9390 vim xxd xxd.c main buffer overflow — vim 5.3 Medium 2025-08-24
CVE-2025-55297 ESF-IDF BluFi Example Memory Overflow Vulnerability — esp-idf 7.4AI High AI 2025-08-21
CVE-2025-9303 TOTOLINK A720R cstecgi.cgi setParentalRules buffer overflow — A720R 8.8 High 2025-08-21
CVE-2011-10025 Subtitle Processor 7.7.1 .m3u SEH Unicode Buffer Overflow — Subtitle Processor 7.8AI High AI 2025-08-20
CVE-2011-10022 SPlayer 3.7 Content-Type Header Buffer Overflow — SPlayer 8.8AI High AI 2025-08-20
CVE-2025-5048 DGN File Parsing Memory Corruption Vulnerability — AutoCAD 7.8 High 2025-08-15
CVE-2025-9023 Tenda AC7/AC18 SetLEDCfg formSetSchedLed buffer overflow — AC7 8.8 High 2025-08-15
CVE-2025-9007 Tenda CH22 editFileName formeditFileName buffer overflow — CH22 8.8 High 2025-08-15
CVE-2025-9006 Tenda CH22 delFileName formdelFileName buffer overflow — CH22 8.8 High 2025-08-15
CVE-2025-20222 Cisco Adaptive Security Appliance Software and Firepower Threat Defense Software Buffer Vulnerability — Cisco Firepower Threat Defense Software 8.6 High 2025-08-14
CVE-2025-8940 Tenda AC20 saveParentControlInfo strcpy buffer overflow — AC20 8.8 High 2025-08-14
CVE-2025-8939 Tenda AC20 WifiGuestSet buffer overflow — AC20 8.8 High 2025-08-14
CVE-2025-8760 INSTAR 2K+/4K fcgi_server base64_decode buffer overflow — 2K+ 9.8 Critical 2025-08-13
CVE-2025-7677 DOS attack possible — Aspect 5.9 Medium 2025-08-11
CVE-2025-8854 bullet3 VHACD utility: stack-based buffer overflow in OFF parser (LoadOFF) — bullet3 7.8AI High AI 2025-08-11
CVE-2025-8736 GNU cflow Lexer c.c yylex buffer overflow — cflow 5.3 Medium 2025-08-08
CVE-2025-6634 TGA File Parsing Memory Corruption Vulnerability — 3ds Max 7.8 High 2025-08-06
CVE-2025-27072 Buffer Copy Without Checking Size of Input in Automotive Vehicle Networks — Snapdragon 5.5 Medium 2025-08-06
CVE-2025-27071 Buffer Copy Without Checking Size of Input in Powerline Communication Firmware — Snapdragon 7.3 High 2025-08-06
CVE-2025-54632 Huawei HarmonyOS和Huawei EMUI 安全漏洞 — HarmonyOS 6.8 Medium 2025-08-06
CVE-2012-10035 Turbo FTP Server 1.30.823/826 PORT Command Buffer Overflow — TurboFTP Server 9.8AI Critical AI 2025-08-05
CVE-2025-53713 TP-Link TL-WR841N WlanNetworkRpm_APC.htm buffer overflow — TL-WR841N V11 7.5AI High AI 2025-07-29
CVE-2025-53712 TP-Link TL-WR841N WlanNetworkRpm_AP.htm buffer overflow — TL-WR841N V11 7.5AI High AI 2025-07-29
CVE-2025-53711 TP-Link TL-WR841N, TL-WR842ND and TL-WR949N WlanNetworkRpm.htm buffer overflow — TL-WR841N v11 7.5AI High AI 2025-07-29
CVE-2025-5038 X_T File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High 2025-07-29
CVE-2025-8246 TOTOLINK X15 HTTP POST Request formRoute buffer overflow — X15 8.8 High 2025-07-27

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