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-2026-0538 GIF File Parsing Out-of-Bounds Write — 3ds Max 7.8 High2026-02-04
CVE-2026-0659 USD File Parsing Out-of-Bounds Write Vulnerability — USD for Arnold 7.8 High2026-02-04
CVE-2026-1788 Buffer Overflow in Xquic Server — Xquic Server 9.8AICriticalAI2026-02-03
CVE-2026-20418 MediaTek Chipsets 安全漏洞 — MediaTek chipset 9.8AICriticalAI2026-02-02
CVE-2026-20417 MediaTek Chipsets 安全漏洞 — MediaTek chipset 6.7AIMediumAI2026-02-02
CVE-2026-20412 MediaTek Chipsets 安全漏洞 — MediaTek chipset 6.7AIMediumAI2026-02-02
CVE-2026-20410 MediaTek Chipsets 安全漏洞 — MediaTek chipset 6.7AIMediumAI2026-02-02
CVE-2026-20409 MediaTek Chipsets 安全漏洞 — MediaTek chipset 6.7AIMediumAI2026-02-02
CVE-2026-20407 MediaTek Chipsets 安全漏洞 — MediaTek chipset 7.8AIHighAI2026-02-02
CVE-2026-20404 MediaTek Chipsets 安全漏洞 — MediaTek chipset 7.5AIHighAI2026-02-02
CVE-2026-20403 MediaTek Chipsets 安全漏洞 — MediaTek chipset 7.5AIHighAI2026-02-02
CVE-2026-20402 MediaTek Chipsets 安全漏洞 — MediaTek chipset 7.5AIHighAI2026-02-02
CVE-2020-37031 Simple Startup Manager 1.17 - 'File' Local Buffer Overflow — Simple Startup Manager 8.4 High2026-01-30
CVE-2026-25061 tcpflow has TIM Element OOB Write in wifipcap — tcpflow 9.8AICriticalAI2026-01-29
CVE-2020-37011 Gnome Fonts Viewer 3.34.0 Heap Corruption — Fonts Viewer 7.5 High2026-01-29
CVE-2020-36964 YATinyWinFTP - Denial of Service — YATinyWinFTP 9.8 Critical2026-01-28
CVE-2025-69419 Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion — OpenSSL 7.8AIHighAI2026-01-27
CVE-2025-68160 Heap out-of-bounds write in BIO_f_linebuffer on short writes — OpenSSL 7.5AIHighAI2026-01-27
CVE-2025-15467 Stack buffer overflow in CMS (Auth)EnvelopedData parsing — OpenSSL 9.8 -2026-01-27
CVE-2025-11187 Improper validation of PBMAC1 parameters in PKCS#12 MAC verification — OpenSSL 8.8AIHighAI2026-01-27
CVE-2026-24832 Out-of-bounds write in ixray-1.6-stcop — ixray-1.6-stcop 9.8 Critical2026-01-27
CVE-2026-1489 Glib: glib: memory corruption via integer overflow in unicode case conversion — Red Hat Enterprise Linux 10 5.4 Medium2026-01-27
CVE-2026-1484 Glib: integer overflow leading to buffer underflow and out-of-bounds write in glib g_base64_encode() — Red Hat Enterprise Linux 10 4.2 Medium2026-01-27
CVE-2026-24829 Out-of-bounds write in is-Engine — is-Engine 6.5 Medium2026-01-27
CVE-2026-24827 Out-of-bounds write in Commander-Genius — Commander-Genius 7.5 High2026-01-27
CVE-2026-24826 Out-of-bounds write in turso3d — turso3d 7.7AIHighAI2026-01-27
CVE-2026-24823 A heap-based buffer over-read or buffer overflow vulnerability in FASTSHIFT/X-TRACK — X-TRACK 9.1AICriticalAI2026-01-27
CVE-2026-24822 a heap-based buffer overflow vulnerability in ttttupup/wxhelper via src/mongoose. — wxhelper 8.4AIHighAI2026-01-27
CVE-2026-24817 A potential heap-buffer overflow in praydog/UEVR — UEVR 8.4AIHighAI2026-01-27
CVE-2026-24809 Save stack space while handling errors in praydog/REFramework — REFramework 9.1AICriticalAI2026-01-27

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