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-2024-12198 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12197 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12193 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12192 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12191 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12178 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-11422 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-12-17
CVE-2024-12668 Velocidex WinPmem Out of Bounds Write Vulnerability — WinPmem 8.2 High2024-12-16
CVE-2024-47615 GHSL-2024-117: GStreamer has an out-of-bounds write in Ogg demuxer — gstreamer 7.1 -2024-12-11
CVE-2024-47541 GHSL-2024-228: GStreamer has an out-of-bounds write in SSA subtitle parser — gstreamer 7.1 -2024-12-11
CVE-2024-47539 GHSL-2024-195: GStreamer has an OOB-write in convert_to_s334_1a — gstreamer 7.8 -2024-12-11
CVE-2024-47537 GHSL-2024-094: GStreamer has an OOB-write in isomp4/qtdemux.c — gstreamer 5.5 -2024-12-11
CVE-2024-53958 Substance3D - Painter | Out-of-bounds Write (CWE-787) — Substance3D - Painter 7.8 High2024-12-10
CVE-2024-53002 Substance3D - Modeler | Out-of-bounds Write (CWE-787) — Substance3D - Modeler 7.8 High2024-12-10
CVE-2024-53000 Substance3D - Modeler | Out-of-bounds Write (CWE-787) — Substance3D - Modeler 7.8 High2024-12-10
CVE-2024-53001 Substance3D - Modeler | Out-of-bounds Write (CWE-787) — Substance3D - Modeler 7.8 High2024-12-10
CVE-2024-53003 Substance3D - Modeler | Out-of-bounds Write (CWE-787) — Substance3D - Modeler 7.8 High2024-12-10
CVE-2024-52994 Substance3D - Sampler | Out-of-bounds Write (CWE-787) — Substance3D - Sampler 7.8 High2024-12-10
CVE-2024-49513 Not a product | Out-of-bounds Write (CWE-787) — Not a product 7.8 High2024-12-10
CVE-2024-49544 InDesign Desktop | Out-of-bounds Write (CWE-787) — InDesign Desktop 7.8 High2024-12-10
CVE-2024-52988 Animate | Out-of-bounds Write (CWE-787) — Animate 7.8 High2024-12-10
CVE-2024-49538 Illustrator | Out-of-bounds Write (CWE-787) — Illustrator 7.8 High2024-12-10
CVE-2024-49553 Media Encoder | Out-of-bounds Write (CWE-787) — Media Encoder 7.8 High2024-12-10
CVE-2024-49551 Media Encoder | Out-of-bounds Write (CWE-787) — Media Encoder 7.8 High2024-12-10
CVE-2024-54091 Siemens Parasolid 缓冲区错误漏洞 — Solid Edge SE2024 7.8 High2024-12-10
CVE-2023-7298 Out-of-Bounds Write Vulnerability in in Autodesk Desktop Software — Autodesk FBX SDK 4.4 Medium2024-12-09
CVE-2024-11156 Rockwell Automation Arena® Out of Bounds Write Vulnerability — Arena® 8.4 -2024-12-05
CVE-2024-8894 Out-of-bounds Write vulnerability in ODA SDK versions < 2025.10 — ODA Drawings SDK - All Versions < 2025.10 7.8 -2024-12-04
CVE-2024-20135 MediaTek Chipsets 安全漏洞 — MT6768, MT6781, MT6833, MT6853, MT6877, MT6878, MT6893, MT6897, MT6989, MT8775, MT8796, MT9687 6.7 -2024-12-02
CVE-2024-20134 MediaTek Chipsets 安全漏洞 — MT6835, MT6878, MT6879, MT6895, MT6896, MT6897, MT6983, MT6985, MT6989, MT8755, MT8775, MT8796, MT8798 6.7 -2024-12-02

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