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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2200 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-2021-43756 Adobe Media Encoder Memory Corruption Vulnerability could lead to Remote Code Execution — Media Encoder 7.8 High2022-06-15
CVE-2021-43754 Adobe Prelude Corruption could lead to Arbitrary code execution — Prelude 7.8 High2022-06-15
CVE-2021-39820 Adobe InDesign Memory Corruption Vulnerability Could Lead to Arbitrary Code Execution — InDesign 7.8 High2022-06-15
CVE-2021-46816 Adobe Premiere Pro M4A file memory corruption vulnerability could lead to remote code execution — Premiere 7.8 High2022-06-13
CVE-2021-46817 Adobe Media Encoder M4A file memory corruption vulnerability could lead to remote code execution — Media Encoder 7.8 High2022-06-13
CVE-2021-46818 Adobe Media Encoder M4A file memory corruption vulnerability could lead to remote code execution — Media Encoder 7.8 High2022-06-13
CVE-2021-37404 Heap buffer overflow in libhdfs native library — Apache Hadoop 9.8 -2022-06-13
CVE-2022-2000 Out-of-bounds Write in vim/vim — vim/vim 7.8 -2022-06-07
CVE-2022-28690 Horner Automation Cscape Csfont — Horner Automation Cscape Csfont 7.8 High2022-06-01
CVE-2022-27184 Horner Automation Cscape Csfont — Horner Automation Cscape Csfont 7.8 High2022-06-01
CVE-2022-1943 Linux kernel 缓冲区错误漏洞 — Kernel 7.8 -2022-06-01
CVE-2022-1897 Out-of-bounds Write in vim/vim — vim/vim 7.8 -2022-05-27
CVE-2021-32969 Delta Electronics DIAScreen - Type Confusion, Out-of-bounds Write — DIAScreen 7.8 High2022-05-24
CVE-2022-29208 Segfault and Out-of-bounds Write write due to incomplete validation in TensorFlow — tensorflow 7.1 High2022-05-20
CVE-2022-1785 Out-of-bounds Write in vim/vim — vim/vim 7.8 -2022-05-19
CVE-2021-42704 Inkscape Out-of-bounds Write — Inkscape 7.8 High2022-05-18
CVE-2022-28182 NVIDIA GPU Display Driver 缓冲区错误漏洞 — NVIDIA GPU Display Driver 8.5 High2022-05-17
CVE-2022-28181 NVIDIA GPU Display Driver 缓冲区错误漏洞 — NVIDIA GPU Display Driver 8.5 High2022-05-17
CVE-2022-28185 NVIDIA GPU Display Driver 缓冲区错误漏洞 — NVIDIA GPU Display Driver 6.8 Medium2022-05-17
CVE-2022-28829 Adobe FrameMaker Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28828 Adobe FrameMaker PDF File Parsing Out-Of-Bounds Write Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28827 Adobe FrameMaker SVG File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28826 Adobe FrameMaker Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28825 Adobe FrameMaker Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28822 Adobe FrameMaker Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28821 Adobe FrameMaker Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — FrameMaker 7.8 -2022-05-13
CVE-2022-28819 Adobe Character Animator SVG File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — Character Animator 7.8 -2022-05-12
CVE-2022-28236 Adobe Acrobat Reader DC Annotation Out-Of-Bounds Write Remote Code Execution Vulnerability — Acrobat Reader 7.8 -2022-05-11
CVE-2022-27798 Adobe Acrobat Reader DC zoomType Out-Of-Bounds Write Remote Code Execution Vulnerability — Acrobat Reader 7.8 -2022-05-11
CVE-2022-27793 Adobe Acrobat Reader DC Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — Acrobat Reader 7.8 -2022-05-11

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