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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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-2025-10899 MODEL File Parsing Out-of-Bounds Write Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-10898 MODEL File Parsing Out-of-Bounds Write Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-10888 MODEL File Parsing Out-of-Bounds Write Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-10884 CATPART File Parsing Out-of-Bounds Write Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-10882 X_T File Parsing Out-of-Bounds Write Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-9456 SLDPRT File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-9452 SLDPRT File Parsing Memory Corruption Vulnerability — Shared Components 7.8 High2025-12-15
CVE-2025-11266 Grassroots DICOM (GDCM) Out-of-bounds Write — DICOM (GDCM) 6.6 Medium2025-12-12
CVE-2025-10451 H19Int15CallbackSmm: SMM memory corruption vulnerability in combined DXE/SMM (SMRAM write) — InsydeH2O 8.2 High2025-12-12
CVE-2025-66590 Out-of-bounds Write vulnerability in AzeoTech DAQFactory — DAQFactory 9.8AICriticalAI2025-12-11
CVE-2020-36885 Sony IPELA Network Camera 1.82.01 Remote Stack Buffer Overflow via ftpclient.cgi — IPELA Network Camera 9.8AICriticalAI2025-12-10
CVE-2021-47719 CNC_Ctrl DllUnregisterServer f5501 Access Violation — COMMAX WebViewer ActiveX Control 9.8AICriticalAI2025-12-09
CVE-2021-47705 CNC_Ctrl DllUnregisterServer Access Violation — COMMAX UMS Client ActiveX Control 8.4AIHighAI2025-12-09
CVE-2025-62550 Azure Monitor Agent Remote Code Execution Vulnerability — Azure Monitor 8.8 High2025-12-09
CVE-2025-42877 Memory Corruption vulnerability in SAP Web Dispatcher, Internet Communication Manager and SAP Content Server — SAP Web Dispatcher, Internet Communication Manager and SAP Content Server 7.5 High2025-12-09
CVE-2025-12196 WatchGuard Firebox Authenticated Out of Bounds Write in Management CLI Ping Command — Fireware OS 6.7AIMediumAI2025-12-04
CVE-2025-12195 WatchGuard Firebox Authenticated Out of Bounds Write in Management CLI IPSec Configuration — Fireware OS 6.7AIMediumAI2025-12-04
CVE-2025-12026 WatchGuard Firebox Authenticated Out of Bounds Write in certd — Fireware OS 6.7AIMediumAI2025-12-04
CVE-2024-45539 Synology DiskStation Manager和Synology Unified Controller 缓冲区错误漏洞 — DiskStation Manager (DSM) 7.5 High2025-12-04
CVE-2025-20777 MediaTek Chipsets 安全漏洞 — MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8186, MT8188, MT8196, MT8667, MT8673, MT8676, MT8678, MT8765, MT8766, MT8768, MT8771, MT8781, MT8791T, MT8792, MT8793, MT8795T, MT8796, MT8798, MT8873, MT8883 6.7AIMediumAI2025-12-02
CVE-2025-20767 MediaTek Chipsets 安全漏洞 — MT2718, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793 6.7AIMediumAI2025-12-02
CVE-2025-20764 MediaTek Chipsets 安全漏洞 — MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793, MT8796, MT8873, MT8893 6.7AIMediumAI2025-12-02
CVE-2025-20763 MediaTek Chipsets 安全漏洞 — MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793, MT8796, MT8873, MT8893 6.7AIMediumAI2025-12-02
CVE-2025-20751 MediaTek Chipsets 安全漏洞 — MT2735, MT6833, MT6833P, MT6853, MT6853T, MT6855, MT6855T, MT6873, MT6875, MT6875T, MT6877, MT6877T, MT6877TT, MT6880, MT6883, MT6885, MT6889, MT6890, MT6891, MT6893, MT8675, MT8771, MT8791, MT8791T, MT8797 7.5AIHighAI2025-12-02
CVE-2025-64129 Zenitel TCIV-3+ Out-of-bounds Write — TCIV-3+ 7.6 High2025-11-26
CVE-2025-64657 Azure Application Gateway Elevation of Privilege Vulnerability — Azure App Gateway 9.8 Critical2025-11-26
CVE-2025-33190 NVIDIA DGX Spark 缓冲区错误漏洞 — DGX Spark 6.7 Medium2025-11-25
CVE-2025-33189 NVIDIA DGX Spark 缓冲区错误漏洞 — DGX Spark 7.8 High2025-11-25
CVE-2025-65084 Out-of-bounds Write in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share — Cobalt 9.8AICriticalAI2025-11-25
CVE-2025-65018 LIBPNG is vulnerable to a heap buffer overflow in `png_combine_row` triggered via `png_image_finish_read` — libpng 7.1 High2025-11-24

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