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-2026-1162 UTT HiPER 810 setSysAdm strcpy buffer overflow — HiPER 810 9.8 Critical2026-01-19
CVE-2026-1158 Totolink LR350 POST Request cstecgi.cgi setWizardCfg buffer overflow — LR350 8.8 High2026-01-19
CVE-2026-1157 Totolink LR350 cstecgi.cgi setWiFiEasyCfg buffer overflow — LR350 8.8 High2026-01-19
CVE-2026-1156 Totolink LR350 cstecgi.cgi setWiFiBasicCfg buffer overflow — LR350 8.8 High2026-01-19
CVE-2026-1155 Totolink LR350 cstecgi.cgi setWiFiEasyGuestCfg buffer overflow — LR350 8.8 High2026-01-19
CVE-2026-1143 TOTOLINK A3700R cstecgi.cgi setWiFiEasyGuestCfg buffer overflow — A3700R 8.8 High2026-01-19
CVE-2026-1140 UTT 进取 520W ConfigExceptAli strcpy buffer overflow — 进取 520W 8.8 High2026-01-19
CVE-2026-1139 UTT 进取 520W ConfigExceptMSN strcpy buffer overflow — 进取 520W 8.8 High2026-01-19
CVE-2026-1138 UTT 进取 520W ConfigExceptQQ strcpy buffer overflow — 进取 520W 8.8 High2026-01-19
CVE-2026-1137 UTT 进取 520W formWebAuthGlobalConfig strcpy buffer overflow — 进取 520W 8.8 High2026-01-19
CVE-2026-1110 cijliu librtsp rtsp_parse_method buffer overflow — librtsp 5.3 Medium2026-01-18
CVE-2026-1109 cijliu librtsp rtsp_parse_request buffer overflow — librtsp 5.3 Medium2026-01-18
CVE-2026-1108 cijliu librtsp rtsp_rely_dumps buffer overflow — librtsp 5.3 Medium2026-01-18
CVE-2021-47815 Nsauditor 3.2.3 - Denial of Service (PoC) — Nsauditor 7.5 High2026-01-15
CVE-2021-47813 Backup Key Recovery 2.2.7 - Denial of Service (PoC) — Backup Key Recovery 7.5 High2026-01-15
CVE-2021-47814 NBMonitor 1.6.8 - Denial of Service (PoC) — NBMonitor 7.5 High2026-01-15
CVE-2021-47798 NoteBurner 2.35 - Denial Of Service (DoS) (PoC) — NoteBurner 9.8 Critical2026-01-15
CVE-2021-47797 Leawo Prof. Media 11.0.0.1 - Denial of Service (DoS) (PoC) — Leawo Prof. Media 7.5 High2026-01-15
CVE-2023-54328 AimOne Video Converter 2.04 Build 103 Buffer Overflow in Registration Form — AimOne Video Converter 6.5 Medium2026-01-13
CVE-2022-50922 Audio Conversion Wizard v2.01 - Buffer Overflow — Audio Conversion Wizard 9.8 Critical2026-01-13
CVE-2026-0841 UTT 进取 520W formPictureUrl strcpy buffer overflow — 进取 520W 8.8 High2026-01-11
CVE-2026-0840 UTT 进取 520W formConfigNoticeConfig strcpy buffer overflow — 进取 520W 8.8 High2026-01-11
CVE-2026-0839 UTT 进取 520W APSecurity strcpy buffer overflow — 进取 520W 8.8 High2026-01-11
CVE-2026-0838 UTT 进取 520W ConfigWirelessBase strcpy buffer overflow — 进取 520W 8.8 High2026-01-11
CVE-2026-0837 UTT 进取 520W formFireWall strcpy buffer overflow — 进取 520W 8.8 High2026-01-11
CVE-2026-0836 UTT 进取 520W formConfigFastDirectionW strcpy buffer overflow — 进取 520W 8.8 High2026-01-11
CVE-2025-47394 Buffer Copy Without Checking Size of Input in DSP Service — Snapdragon 7.8 High2026-01-06
CVE-2025-47388 Buffer Copy without Checking Size of Input in DSP Service — Snapdragon 7.8 High2026-01-06
CVE-2025-47335 Buffer Copy Without Checking Size of Input in Camera Driver — Snapdragon 6.7 Medium2026-01-06
CVE-2025-47334 Buffer Copy Without Checking Size of Input in Camera Driver — Snapdragon 6.7 Medium2026-01-06

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