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-2022-23187 Adobe Illustrator 2022 Buffer Overflow could lead to Arbitrary code execution — Illustrator 7.8 High2022-03-11
CVE-2022-24754 Buffer overflow in pjsip — pjproject 8.5 High2022-03-11
CVE-2022-22805 Schneider Electric 多款产品缓冲区错误漏洞 — SmartConnect 9.8 -2022-03-09
CVE-2022-21716 Buffer Overflow in Twisted — twisted 7.5 High2022-03-03
CVE-2022-23203 Adobe Photoshop Buffer Overflow could lead to Arbitrary code execution — Photoshop 7.8 High2022-02-16
CVE-2022-23188 Adobe Illustrator Buffer Overflow could lead to Arbitrary code execution — Illustrator 7.8 High2022-02-16
CVE-2021-43303 PJSUA API 安全漏洞 — pjsip 9.8 -2022-02-16
CVE-2021-22824 Schneider Electric Interactive Graphical SCADA System 缓冲区错误漏洞 — Interactive Graphical SCADA System Data Collector (dc.exe) (V15.0.0.21320 and prior) 7.5 -2022-02-11
CVE-2021-22802 Schneider Electric IGSS 安全漏洞 — Interactive Graphical SCADA System Data Collector (dc.exe) (V15.0.0.21243 and prior) 9.8 -2022-02-11
CVE-2022-23431 Google Android 安全漏洞 — Samsung Mobile Devices with Exynos chipsets 6.4 Medium2022-02-11
CVE-2022-23428 Google Android 安全漏洞 — Samsung Mobile Devices with Exynos chipsets 8.4 High2022-02-11
CVE-2022-24313 Schneider Electric Interactive Graphical SCADA System 安全漏洞 — Interactive Graphical SCADA System Data Server (V15.0.0.22020 and prior) 9.8 -2022-02-09
CVE-2022-22725 Schneider Electric Easergy P3 缓冲区错误漏洞 — Easergy P3 (All versions prior to V30.205) 8.8 -2022-02-04
CVE-2022-22723 Schneider Electric Easergy P5 缓冲区错误漏洞 — Easergy P5 (All firmware versions prior to V01.401.101) 8.8 -2022-02-04
CVE-2021-21970 Sealevel Systems SeaConnect 370w 缓冲区错误漏洞 — Sealevel 8.1 -2022-02-04
CVE-2021-21969 Sealevel Systems SeaConnect 370w 缓冲区错误漏洞 — Sealevel" 8.1 -2022-02-04
CVE-2021-38692 Stack Overflow Vulnerability in QVR Elite, QVR Pro and QVR Guard — QVR Elite 8.1 High2022-01-14
CVE-2021-38691 Stack Overflow Vulnerability in QVR Elite, QVR Pro and QVR Guard — QVR Elite 8.1 High2022-01-14
CVE-2021-38690 Stack Overflow Vulnerability in QVR Elite, QVR Pro and QVR Guard — QVR Elite 8.1 High2022-01-14
CVE-2021-38689 Stack Overflow Vulnerability in QVR Elite, QVR Pro and QVR Guard — QVR Elite 8.1 High2022-01-14
CVE-2021-38682 Stack Overflow Vulnerability in QVR Elite, QVR Pro and QVR Guard — QVR Elite 8.1 High2022-01-14
CVE-2021-34979 NETGEAR R6260 安全漏洞 — R6260 8.8 -2022-01-13
CVE-2021-38687 Stack Overflow Vulnerability in Surveillance Station — Surveillance Station 8.1 High2021-12-29
CVE-2021-21903 Garrett Metal Detectors 缓冲区错误漏洞 — Garrett Metal Detectors 9.8 -2021-12-22
CVE-2021-21901 Garrett Metal Detectors 缓冲区错误漏洞 — Garrett Metal Detectors 9.8 -2021-12-22
CVE-2021-42757 Fortinet FortiOS 缓冲区错误漏洞 — FortiOS 6.3 Medium2021-12-08
CVE-2021-20045 SonicWall SMA100 安全漏洞 — SonicWall SMA100 9.8 -2021-12-08
CVE-2021-42785 Buffer Overflow in tvnviewer.exe via Crafted Packet in TightVNC Viewer 2.8.59 — TightVNC Viewer 9.8 -2021-11-23
CVE-2021-36333 Dell EMC CloudLink 安全漏洞 — CloudLink 5.5 Medium2021-11-23
CVE-2021-42731 Adobe Indesign Buffer Overflow Could Lead to Remote Code Execution — InDesign 7.8 High2021-11-16

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