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-3346 Tenda AC7 SetPptpServerCfg formSetPPTPServer buffer overflow — AC7 8.8 High2025-04-07
CVE-2024-58110 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.6 Medium2025-04-07
CVE-2024-58109 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.6 Medium2025-04-07
CVE-2024-58108 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.6 Medium2025-04-07
CVE-2024-58106 Huawei HarmonyOS 安全漏洞 — HarmonyOS 4.6 Medium2025-04-07
CVE-2025-3328 Tenda AC1206 fast_setting_wifi_set form_fast_setting_wifi_set buffer overflow — AC1206 8.8 High2025-04-07
CVE-2025-3194 bigint-buffer 安全漏洞 — bigint-buffer 7.5 High2025-04-04
CVE-2025-3148 codeprojects Product Management System Login buffer overflow — Product Management System 3.3 Low2025-04-03
CVE-2025-3139 code-projects Bus Reservation System Login Form login buffer overflow — Bus Reservation System 5.3 Medium2025-04-03
CVE-2025-1660 DWFX File Parsing Memory Corruption Vulnerability — Navisworks Freedom 7.8 High2025-04-01
CVE-2023-33302 Fortinet FortiMail 安全漏洞 — FortiNDR 4.5 Medium2025-03-31
CVE-2025-1430 SLDPRT File Parsing Memory Corruption Vulnerability — AutoCAD 7.8 High2025-03-13
CVE-2025-20115 Cisco IOS XR Software Border Gateway Protocol Denial of Service Vulnerability — Cisco IOS XR Software 8.6 High2025-03-12
CVE-2025-2017 Ashlar-Vellum Cobalt CO File Parsing Buffer Overflow Remote Code Execution Vulnerability — Cobalt 7.8 -2025-03-11
CVE-2024-53695 HBS 3 Hybrid Backup Sync — HBS 3 Hybrid Backup Sync 9.1 -2025-03-07
CVE-2025-23234 Arkcompiler Ets Runtime has a buffer overflow vulnerability — OpenHarmony 3.3 Low2025-03-04
CVE-2025-22897 Arkcompiler Ets Runtime has a buffer overflow vulnerability — OpenHarmony 3.3 Low2025-03-04
CVE-2025-1899 Tenda TX3 setPptpUserList buffer overflow — TX3 6.5 Medium2025-03-04
CVE-2025-1898 Tenda TX3 openSchedWifi buffer overflow — TX3 6.5 Medium2025-03-04
CVE-2025-1897 Tenda TX3 SetNetControlList buffer overflow — TX3 6.5 Medium2025-03-04
CVE-2025-1896 Tenda TX3 SetStaticRouteCfg buffer overflow — TX3 6.5 Medium2025-03-04
CVE-2025-1895 Tenda TX3 setMacFilterCfg buffer overflow — TX3 6.5 Medium2025-03-04
CVE-2025-0689 Grub2: udf: heap based buffer overflow in grub_udf_read_block() may lead to arbitrary code execution 7.8 High2025-03-03
CVE-2024-53027 Buffer Copy Without Checking Size of Input in WLAN Host — Snapdragon 7.5 High2025-03-03
CVE-2024-43055 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Camera_Linux — Snapdragon 7.8 High2025-03-03
CVE-2025-25280 Century Systems FutureNet AS series和Century Systems FutureNet FA series 安全漏洞 — FutureNet AS-250/S 5.3 Medium2025-03-03
CVE-2025-1852 Totolink EX1800T cstecgi.cgi loginAuth buffer overflow — EX1800T 8.8 High2025-03-03
CVE-2025-1786 rizinorg rizin pdb.c msf_stream_directory_free buffer overflow — rizin 5.3 Medium2025-03-01
CVE-2025-1587 SourceCodester Telecom Billing Management System Add New Record main.cpp addrecords buffer overflow — Telecom Billing Management System 5.3 Medium2025-02-23
CVE-2025-1372 GNU elfutils eu-readelf readelf.c print_string_section buffer overflow — elfutils 5.3 Medium2025-02-17

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