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-2025-12051 H2OFFT64.sys is potentially vulnerable to a buffer overflow. — InsydeH2O tools 7.8 High2026-01-14
CVE-2025-12050 In H2OFFT32.sys is potentially vulnerable to a buffer overflow. — InsydeH2O tools 7.8 High2026-01-14
CVE-2026-21299 Substance3D - Modeler | Out-of-bounds Write (CWE-787) — Substance3D - Modeler 7.8 High2026-01-13
CVE-2026-21298 Substance3D - Modeler | Out-of-bounds Write (CWE-787) — Substance3D - Modeler 7.8 High2026-01-13
CVE-2026-21307 Substance3D - Designer | Out-of-bounds Write (CWE-787) — Substance3D - Designer 7.8 High2026-01-13
CVE-2026-21306 Substance3D - Sampler | Out-of-bounds Write (CWE-787) — Substance3D - Sampler 7.8 High2026-01-13
CVE-2026-21305 Substance3D - Painter | Out-of-bounds Write (CWE-787) — Substance3D - Painter 7.8 High2026-01-13
CVE-2026-21897 CryptoLib Has Out-of-Bounds Write in Crypto_Config_Add_Gvcid_Managed_Parameters — CryptoLib 7.3 High2026-01-10
CVE-2026-21869 llama.cpp has Out-of-bounds Write in llama-server — llama.cpp 8.8 High2026-01-07
CVE-2026-22184 zlib <= 1.3.1.2 untgz Global Buffer Overflow in TGZfname() — zlib 9.8 -2026-01-07
CVE-2025-47346 Out-of-bounds Write in HLOS — Snapdragon 7.8 High2026-01-06
CVE-2025-20783 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-20782 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-20778 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-20800 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-20798 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-20795 MediaTek chipsets 安全漏洞 — MediaTek chipset 6.7 -2026-01-06
CVE-2025-11964 OOBW in utf_16le_to_utf_8_truncated() in libpcap — libpcap 1.9 Low2025-12-31
CVE-2025-15359 DVP-12SE11T - Out-of-bound memory write Vulnerability — DVP-12SE11T 9.1 Critical2025-12-30
CVE-2025-14178 Heap buffer overflow in array_merge() — PHP 6.5 Medium2025-12-27
CVE-2025-68474 ESF-IDF Has Out-of-Bounds Write in ESP32 Bluetooth AVRCP Vendor Command Handling — esp-idf 7.5 -2025-12-26
CVE-2025-68473 ESF-IDF Has Out-of-Bounds Read in ESP32 Bluetooth SDP Result Handling — esp-idf 6.5 -2025-12-26
CVE-2018-25154 GNU Barcode 0.99 Buffer Overflow in Code 93 Encoding Mechanism — GNU Barcode 9.8 Critical2025-12-24
CVE-2025-14409 Soda PDF Desktop PDF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — Desktop 7.8AIHighAI2025-12-23
CVE-2025-14733 WatchGuard Firebox iked Out of Bounds Write Vulnerability — Fireware OS 9.8 -2025-12-19
CVE-2025-68381 Packetbeat Improper Bounds Check — Packetbeat 6.5 Medium2025-12-18
CVE-2025-64461 Out of Bounds Write in mgocre_SH_25_3!RevBL() in NI LabVIEW — LabVIEW 7.8 High2025-12-18
CVE-2025-47320 Out-of-bounds Write in Audio — Snapdragon 7.8 High2025-12-18
CVE-2025-53524 Fuji Electric Monitouch V-SFT-6 Out-of-bounds Write — Monitouch V-SFT-6 7.8 High2025-12-17
CVE-2025-10900 MODEL File Parsing Out-of-Bounds Write Vulnerability — Shared Components 7.8 High2025-12-15

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