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-2024-9533 D-Link DIR-605L formDeviceReboot buffer overflow — DIR-605L 8.8 High2024-10-05
CVE-2024-9532 D-Link DIR-605L formAdvanceSetup buffer overflow — DIR-605L 8.8 High2024-10-05
CVE-2024-9515 D-Link DIR-605L formSetQoS buffer overflow — DIR-605L 8.8 High2024-10-04
CVE-2024-9514 D-Link DIR-605L formSetDomainFilter buffer overflow — DIR-605L 8.8 High2024-10-04
CVE-2022-49041 多款产品安全漏洞 — Synology Drive Client 4.4 Medium2024-09-26
CVE-2022-49040 Synology Drive 安全漏洞 — Synology Drive Client 4.4 Medium2024-09-26
CVE-2023-52946 Synology Drive 安全漏洞 — Synology Drive Client 8.2 High2024-09-26
CVE-2024-23972 Sony XAV-AX5500 USB Configuration Descriptor Buffer Overflow Remote Code Execution Vulnerability — XAV-AX5500 6.8 Medium2024-09-23
CVE-2024-9088 SourceCodester Telecom Billing Management System login buffer overflow — Telecom Billing Management System 6.3 Medium2024-09-22
CVE-2024-24972 Controller 6000和Controller 7000安全漏洞 — Controller 6000 and Controller 7000 6.5 Medium2024-09-11
CVE-2024-8579 TOTOLINK AC1200 T8 cstecgi.cgi setWiFiRepeaterCfg buffer overflow — AC1200 T8 8.8 High2024-09-08
CVE-2024-8578 TOTOLINK AC1200 T8 cstecgi.cgi setWiFiMeshName buffer overflow — AC1200 T8 8.8 High2024-09-08
CVE-2024-8577 TOTOLINK AC1200 T8/AC1200 T10 cstecgi.cgi setStaticDhcpRules buffer overflow — AC1200 T8 8.8 High2024-09-08
CVE-2024-8576 TOTOLINK AC1200 T8/AC1200 T10 cstecgi.cgi setIpPortFilterRules buffer overflow — AC1200 T8 8.8 High2024-09-08
CVE-2024-8575 TOTOLINK AC1200 T8 cstecgi.cgi setWiFiScheduleCfg buffer overflow — AC1200 T8 8.8 High2024-09-08
CVE-2024-8573 TOTOLINK AC1200 T8/AC1200 T10 cstecgi.cgi setParentalRules buffer overflow — AC1200 T8 8.8 High2024-09-08
CVE-2024-32763 QTS, QuTS hero — QTS 8.8 -2024-09-06
CVE-2023-51367 QTS, QuTS hero — QTS 5.4 Medium2024-09-06
CVE-2024-45620 Libopensc: incorrect handling of the length of buffers or files in pkcs15init 3.9 Low2024-09-03
CVE-2024-45619 Libopensc: incorrect handling length of buffers or files in libopensc 4.3 Medium2024-09-03
CVE-2024-6343 Zyxel多款产品 安全漏洞 — ATP series firmware 4.9 Medium2024-09-03
CVE-2024-5412 Zyxel VMG8825-T50K 安全漏洞 — VMG8825-T50K firmware 7.5 High2024-09-03
CVE-2024-33054 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Computer Vision — Snapdragon 7.8 High2024-09-02
CVE-2024-33052 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in FM Host — Snapdragon 7.8 High2024-09-02
CVE-2024-33042 Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in FM Host — Snapdragon 7.8 High2024-09-02
CVE-2024-41176 Beckhoff: Local Denial of Service issue in package MDP included in TwinCAT/BSD — MDP package 7.3 High2024-08-27
CVE-2024-8079 TOTOLINK AC1200 T8 exportOvpn buffer overflow — AC1200 T8 8.8 High2024-08-22
CVE-2024-8078 TOTOLINK AC1200 T8 setTracerouteCfg buffer overflow — AC1200 T8 8.8 High2024-08-22
CVE-2024-8076 TOTOLINK AC1200 T8 setDiagnosisCfg buffer overflow — AC1200 T8 8.8 High2024-08-22
CVE-2024-6918 Schneider Electric Accutech Manager 安全漏洞 — Accutech Manager 7.5 High2024-08-20

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