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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1911 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-11516 UTT HiPER 2610G formNatStaticMap strcpy buffer overflow — HiPER 2610G 5.5 Medium 2026-06-08
CVE-2019-25741 Mobatek MobaXterm 12.1 Buffer Overflow via Sessions File — Mobatek MobaXterm 9.8 Critical 2026-06-04
CVE-2019-25736 LabF nfsAxe 3.7 Ping Client Buffer Overflow — LabF nfsAxe 8.4 High 2026-06-04
CVE-2019-25735 AllPlayer 7.4 Local Buffer Overflow via SEH Unicode — AllPlayer 8.4 High 2026-06-04
CVE-2019-25733 NetShareWatcher 1.5.8.0 SEH Buffer Overflow — NetShareWatcher 8.4 High 2026-06-04
CVE-2026-3871 Zyxel VMG4005-B50B 安全漏洞 — VMG4005-B50B firmware 6.5 Medium 2026-06-02
CVE-2026-3870 Zyxel VMG4005-B50B 安全漏洞 — VMG4005-B50B firmware 6.5 Medium 2026-06-02
CVE-2026-25277 Buffer Copy Without Checking Size of Input in Secure Processor — Snapdragon 8.8 High 2026-06-01
CVE-2018-25432 Arm Whois 3.11 Buffer Overflow via ASLR Bypass — Arm Whois 8.4 High 2026-06-01
CVE-2026-10275 OpenSC pkcs11-tool Key Generation pkcs11-tool.c test_kpgen_certwrite buffer overflow — OpenSC 5.0 Medium 2026-06-01
CVE-2026-10164 Edimax BR-6478AC POST Request formUSBFolder buffer overflow — BR-6478AC 8.8 High 2026-05-31
CVE-2026-10163 Edimax BR-6478AC POST Request formUSBAccount buffer overflow — BR-6478AC 8.8 High 2026-05-31
CVE-2026-10126 Edimax BR-6478AC POST Request formQoS buffer overflow — BR-6478AC 8.8 High 2026-05-30
CVE-2018-25426 WinMTR 0.91 Denial of Service via Buffer Overflow — WinMTR 7.5 High 2026-05-30
CVE-2018-25423 Arm Whois 3.11 Denial of Service via Buffer Overflow — Arm Whois 6.2 Medium 2026-05-30
CVE-2025-12686 Synology BeeStation OS 安全漏洞 — BeeStation OS 9.8 Critical 2026-05-27
CVE-2026-9627 UTT HiPER 1200GW Web Management setSysAdm strcpy buffer overflow — HiPER 1200GW 8.8 High 2026-05-27
CVE-2026-7454 WRL File Parsing Memory Corruption in Autodesk 3ds Max — 3ds Max 7.8 High 2026-05-26
CVE-2026-7452 WRL File Parsing Memory Corruption in Autodesk 3ds Max — 3ds Max 7.8 High 2026-05-26
CVE-2018-25377 Flash Slideshow Maker Professional 5.20 Buffer Overflow SEH — Flash Slideshow Maker Professional 8.4 High 2026-05-25
CVE-2018-25376 Socusoft 3GP Photo Slideshow 8.05 Buffer Overflow SEH — 3GP Photo Slideshow 8.4 High 2026-05-25
CVE-2018-25369 Visual Ping 0.8.0.0 Buffer Overflow Denial of Service — Visual Ping 6.2 Medium 2026-05-25
CVE-2018-25367 NASA openVSP 3.16.1 Denial of Service via Buffer Overflow — openVSP 6.2 Medium 2026-05-25
CVE-2018-25366 CuteFTP 5.0 XP Buffer Overflow via Site Manager Label Field — CuteFTP 8.4 High 2026-05-25
CVE-2026-9443 Edimax BR-6478AC POST Request formL2TPSetup buffer overflow — BR-6478AC 8.8 High 2026-05-25
CVE-2026-9442 Edimax BR-6478AC POST Request formiNICSiteSurvey buffer overflow — BR-6478AC 8.8 High 2026-05-25
CVE-2026-9403 Edimax BR-6675nD POST Request formWlSiteSurvey buffer overflow — BR-6675nD 8.8 High 2026-05-24
CVE-2026-9401 Edimax BR-6675nD POST Request formWanTcpipSetup buffer overflow — BR-6675nD 8.8 High 2026-05-24
CVE-2026-9399 Edimax BR-6675nD POST Request formsetPPPoE buffer overflow — BR-6675nD 8.8 High 2026-05-24
CVE-2026-9393 H3C Magic B0 aspForm Edit_BasicSSID_5G buffer overflow — Magic B0 8.8 High 2026-05-24

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