Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-120 (未进行输入大小检查的缓冲区拷贝(传统缓冲区溢出)) — Vulnerability Class 1910

1910 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-2026-71941 DrayTek VigorSwitch Multiple Models Buffer Overflow via diag_logmail — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71942 DrayTek VigorSwitch Multiple Models Buffer Overflow via mail_mailalert — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71940 DrayTek VigorSwitch Multiple Models Buffer Overflow via acl_general_setup Edit ACE — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71939 DrayTek VigorSwitch Multiple Models Buffer Overflow via acl_general_setup Add ACE — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71938 DrayTek VigorSwitch Multiple Models Buffer Overflow via switch_lan_gvrp — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71937 DrayTek VigorSwitch Multiple Models Buffer Overflow via poe_schedule_profile — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71936 DrayTek VigorSwitch Multiple Models Buffer Overflow via sysreboot — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71935 DrayTek VigorSwitch Multiple Models Buffer Overflow via webBackupAction — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71934 DrayTek VigorSwitch Multiple Models Buffer Overflow via pingtrace — VigorSwitch G2540xs 7.2 High 2026-08-24
CVE-2026-71912 DrayTek VigorAP Multiple Models Buffer Overflow via apautotest — VigorAP 918R 7.2 High 2026-08-24
CVE-2026-71911 DrayTek VigorAP Multiple Models Buffer Overflow via setLan — VigorAP 918R 7.2 High 2026-08-24
CVE-2026-78170 UTT HiPER 1200GW formConfigFastDirectionW strcpy buffer overflow — HiPER 1200GW 8.8 High 2026-08-24
CVE-2026-68768 hashcat through 7.1.2 Heap Buffer Overflow in outfile_write() via Oversized Username — hashcat 6.1 Medium 2026-08-22
CVE-2026-17040 Vulnerabilities in IBM AIX and PowerVM VIOS — AIX 9.8 Critical 2026-08-20
CVE-2026-18280 Sony XAV-9500ES gpsd Buffer Overflow Arbitrary Code Execution Vulnerability — XAV-9500ES - - 2026-08-20
CVE-2026-18279 Sony XAV-9500ES RTSP SETUP Buffer Overflow Remote Code Execution Vulnerability — XAV-9500ES - - 2026-08-20
CVE-2026-20302 Cisco RoomOS Stack Overflow Vulnerability — Cisco RoomOS Software 6.1 Medium 2026-08-19
CVE-2026-14970 Vulnerabilities in IBM AIX and PowerVM VIOS — AIX 7.5 High 2026-08-19
CVE-2026-24184 NVIDIA Cumulus Linux LLDP守护进程缓冲区溢出漏洞 — Cumulus Linux GA 7.5 High 2026-08-18
CVE-2026-70415 Dell PowerStore 缓冲区错误漏洞 — PowerStore 500T 8.1 High 2026-08-18
CVE-2026-19999 Open Asset Import Library Assimp 3DGS MDL7 Bone Transformation Key MDLLoader.cpp ParseBoneTrafoKeys_3DGS_MDL7 buffer overflow — Assimp 6.3 Medium 2026-08-17
CVE-2026-19969 Open Asset Import Library Assimp 3DGS MDL7 Model Output Mesh Generator MDLLoader.cpp GenerateOutputMeshes_3DGS_MDL7 buffer overflow — Assimp 5.4 Medium 2026-08-17
CVE-2026-19961 Edimax EW-7478APC formWlSiteSurvey buffer overflow — EW-7478APC 9.9 Critical 2026-08-16
CVE-2026-19821 Tenda AC12 httpd web management interface SetSysAutoRebbotCfg formSetRebootTimer buffer overflow — AC12 8.8 High 2026-08-14
CVE-2026-19792 Tenda G0 httpd web management interface module setPortMapping buffer overflow — G0 8.8 High 2026-08-14
CVE-2026-17220 IBM i is Affected By Multiple Vulnerabilities in Host Servers — i 8.2 High 2026-08-13
CVE-2026-19002 Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver — BI Connector ODBC Driver 8.1 High 2026-08-12
CVE-2026-70465 Fortinet forticlientwindows 缓冲区错误漏洞 — FortiClientWindows 7.3 High 2026-08-12
CVE-2025-41769 Unauthenticated Buffer Overflow in PROFINET Service — AXC F 1152 9.8 Critical 2026-08-12
CVE-2024-14044 Open5GS Diameter Rx pcrf-rx-path.c pcrf_rx_aar_cb buffer overflow — Open5GS 6.3 Medium 2026-08-12

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