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-2021-3056 PAN-OS: Memory Corruption Vulnerability in GlobalProtect Clientless VPN During SAML Authentication — PAN-OS 8.8 High2021-11-10
CVE-2021-41221 Access to invalid memory during shape inference in `Cudnn*` ops — tensorflow 7.8 High2021-11-05
CVE-2021-41216 Heap buffer overflow in `Transpose` — tensorflow 5.5 Medium2021-11-05
CVE-2021-43082 heap-buffer-overflow with stats-over-http plugin — Apache Traffic Server 9.8 -2021-11-03
CVE-2021-34775 Cisco Small Business 220 Series Smart Switches Link Layer Discovery Protocol Vulnerabilities — Cisco Small Business 200 Series Smart Switches 4.3 Medium2021-10-06
CVE-2021-34776 Cisco Small Business 220 Series Smart Switches Link Layer Discovery Protocol Vulnerabilities — Cisco Small Business 200 Series Smart Switches 4.3 Medium2021-10-06
CVE-2021-34777 Cisco Small Business 220 Series Smart Switches Link Layer Discovery Protocol Vulnerabilities — Cisco Small Business 200 Series Smart Switches 4.3 Medium2021-10-06
CVE-2021-34778 Cisco Small Business 220 Series Smart Switches Link Layer Discovery Protocol Vulnerabilities — Cisco Small Business 200 Series Smart Switches 4.3 Medium2021-10-06
CVE-2021-34779 Cisco Small Business 220 Series Smart Switches Link Layer Discovery Protocol Vulnerabilities — Cisco Small Business 200 Series Smart Switches 4.3 Medium2021-10-06
CVE-2021-34780 Cisco Small Business 220 Series Smart Switches Link Layer Discovery Protocol Vulnerabilities — Cisco Small Business 200 Series Smart Switches 4.3 Medium2021-10-06
CVE-2021-25498 Samsung Notes 安全漏洞 — Samsung Notes 7.3 High2021-10-06
CVE-2021-25497 Samsung Notes 安全漏洞 — Samsung Notes 7.3 High2021-10-06
CVE-2021-25496 Samsung Notes 安全漏洞 — Samsung Notes 7.3 High2021-10-06
CVE-2021-25469 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 6.0 Medium2021-10-06
CVE-2021-25467 Samsung SMR 安全漏洞 — Samsung Mobile Devices 5.3 Medium2021-10-06
CVE-2021-40709 Adobe Photoshop Buffer Overflow leads to Arbitrary Code Execution — Photoshop 7.8 High2021-09-27
CVE-2021-33035 Buffer overflow from a crafted DBF file — Apache OpenOffice 7.8 -2021-09-23
CVE-2021-34727 Cisco IOS XE SD-WAN Software Buffer Overflow Vulnerability — Cisco IOS XE SD-WAN Software 9.8 Critical2021-09-23
CVE-2021-31844 Local Privilege Escalation in McAfee DLP Endpoint for Windows — McAfee Data Loss Prevention (DLP) Endpoint for Windows 8.2 High2021-09-17
CVE-2021-31845 Remote Code Execution in McAfee DLP Discover — McAfee Data Loss Prevention (DLP) Discover 8.4 High2021-09-17
CVE-2021-33720 Siemens SIPROTEC 5 代码注入漏洞 — SIPROTEC 5 relays with CPU variants CP050 7.5 -2021-09-14
CVE-2021-33719 Siemens SIPROTEC 5 代码注入漏洞 — SIPROTEC 5 relays with CPU variants CP050 9.8 -2021-09-14
CVE-2021-27391 Siemens APOGEE MBC 缓冲区错误漏洞 — APOGEE MBC (PPC) (P2 Ethernet) 9.8 -2021-09-14
CVE-2021-25461 Samsung SMR 缓冲区错误漏洞 — Samsung Mobile Devices 4.0 Medium2021-09-09
CVE-2021-28580 Medium by Adobe file parsing buffer overflow vulnerability could lead to arbitrary code execution — Medium 8.8 High2021-09-08
CVE-2020-7877 ZOOK solution(remote administration tool) buffer overflow vulnerability — ZOOKViewer_Setup.exe 8.0 High2021-09-07
CVE-2021-36075 Adobe Bridge Buffer Overflow leads to Arbitrary Code Execution — Bridge 7.8 High2021-09-01
CVE-2021-21828 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T 9.8 -2021-08-20
CVE-2021-21827 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T 9.8 -2021-08-20
CVE-2021-21826 AT&T Labs Xmill 缓冲区错误漏洞 — AT&T 9.8 -2021-08-20

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