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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-787 (跨界内存写) — Vulnerability Class 2231

2231 vulnerabilities classified as CWE-787 (跨界内存写). AI Chinese analysis included.

CWE-787 represents a critical memory management weakness where software incorrectly writes data beyond the allocated boundaries of a buffer. This flaw typically arises from insufficient bounds checking, allowing attackers to overwrite adjacent memory locations with malicious payloads. Exploitation often leads to arbitrary code execution, denial of service, or privilege escalation by corrupting critical system structures or control flow data. Developers mitigate this risk by implementing rigorous input validation and utilizing safe programming practices that enforce strict boundary checks before any memory operation. Employing modern languages with automatic memory management, such as Rust or Java, further reduces exposure by preventing direct pointer arithmetic. Additionally, static analysis tools and fuzzing techniques help identify potential out-of-bounds conditions during the development lifecycle, ensuring that buffer operations remain within their intended limits and preserving application integrity against memory corruption attacks.

MITRE CWE Description
The product writes data past the end, or before the beginning, of the intended buffer.
Common Consequences (3)
IntegrityModify Memory, Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
AvailabilityDoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
OtherUnexpected State
Subsequent write operations can produce undefined or unexpected results.
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 the buffer is as large as specified. 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 in a…
Operation, Build and CompilationRun or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported…
Effectiveness: Defense in Depth
Examples (2)
The following code attempts to save four different identification numbers into an array.
int id_sequence[3]; /* Populate the id array. */ id_sequence[0] = 123; id_sequence[1] = 234; id_sequence[2] = 345; id_sequence[3] = 456;
Bad · C
In the following code, it is possible to request that memcpy move a much larger segment of memory than assumed:
int returnChunkSize(void *) { /* if chunk info is valid, return the size of usable memory, * else, return -1 to indicate an error */ ... } int main() { ... memcpy(destBuf, srcBuf, (returnChunkSize(destBuf)-1)); ... }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2023-26373 Adobe Dimension has an arbitrary address write vulnerability when parsing USDZ files — Dimension 7.8 High2023-04-12
CVE-2023-26395 Adobe Acrobat parsing PDF Out-of-bounds Write Arbitrary code execution — Acrobat Reader 7.8 High2023-04-12
CVE-2023-1801 tcpdump 缓冲区错误漏洞 — tcpdump 8.1 -2023-04-07
CVE-2023-0186 NVIDIA GPU Display Driver for Windows 缓冲区错误漏洞 — vGPU software (guest driver - Windows), NVIDIA Cloud Gaming (guest driver - Windows) 6.1 Medium2023-04-01
CVE-2023-0183 NVIDIA GPU Display Driver for Linux 缓冲区错误漏洞 — vGPU software (guest driver - Linux), vGPU software (Virtual GPU Manager - Citrix Hypervisor, VMware vSphere, Red Hat Enterprise Linux KVM), NVIDIA Cloud Gaming (guest driver - Linux), NVIDIA Cloud Gaming (Virtual GPU Manager - Red Hat Enterprise Linux KVM) 7.1 High2023-04-01
CVE-2023-0182 NVIDIA GPU Display Driver for Windows 缓冲区错误漏洞 — vGPU software (guest driver - Windows), NVIDIA Cloud Gaming (guest driver - Windows) 7.8 High2023-04-01
CVE-2022-28300 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation 7.8 -2023-03-29
CVE-2022-28301 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28314 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28316 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28318 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28642 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28643 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28644 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-28646 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-29
CVE-2022-37354 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37355 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37356 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37357 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37358 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37362 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37364 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37369 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37371 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-37372 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-03-29
CVE-2022-43614 Corel CorelDRAW Graphics Suite 缓冲区错误漏洞 — CorelDRAW Graphics Suite 7.8 -2023-03-29
CVE-2022-43617 Corel CorelDRAW Graphics Suite 缓冲区错误漏洞 — CorelDRAW Graphics Suite 7.8 -2023-03-29
CVE-2022-43618 Corel CorelDRAW Graphics Suite 缓冲区错误漏洞 — CorelDRAW Graphics Suite 7.8 -2023-03-29
CVE-2022-1229 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2023-03-28
CVE-2023-25880 ZDI-CAN-19412: Adobe Dimension GLTF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — Dimension 7.8 High2023-03-28

Vulnerabilities classified as CWE-787 (跨界内存写) represent 2231 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.