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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

3158 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)
Integrity Modify 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.
Availability DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Mitigations (5)
Requirements Use 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 Design Use 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 Compilation Use 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
Implementation Consider 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 Compilation Run 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 ID Title CVSS Severity Published
CVE-2026-86377 Dell PowerProtect Data Domain 多版本越界写漏洞 — PowerProtect Data Domain 7.6 High 2026-10-28
CVE-2026-118435 三星 escargot 越界写漏洞致缓冲区操纵 — escargot 5.4 Medium 2026-10-28
CVE-2026-118375 llama.cpp b8841 before b11865 Stack-based Buffer Overflow via ggml-rpc RDMA rdma_recv() — llama.cpp 8.1 High 2026-10-28
CVE-2026-118335 Chrome 156.0.8078.73 之前版本 Metrics 输入验证漏洞 — Chrome - - 2026-10-27
CVE-2026-118313 Chrome 156.0.8078.73 前版本视频 Use-After-Free 漏洞 — Chrome - - 2026-10-27
CVE-2026-57199 Asterisk: Asterisk app_sms.c copies externally controlled SMS lengths into fixed in-struct buffers — asterisk 2.3 Low 2026-10-27
CVE-2026-57188 Asterisk: Stack buffer overflow in res_xmpp XMPP namespace prefix handling — asterisk 7.1 High 2026-10-27
CVE-2026-57189 Asterisk: Possible RED T.140 Generation Accumulation OOB Write — asterisk 2.3 Low 2026-10-27
CVE-2026-57201 Asterisk: Stack Buffer Overflow in H.323 ooTrace() via Unbounded vsprintf into Fixed 2048-byte Buffer — asterisk 7.5 High 2026-10-27
CVE-2026-57194 Asterisk: chan_unistim DIALPAGE digit handling can overflow phone_number and crash Asterisk — asterisk 5.9 Medium 2026-10-27
CVE-2026-107590 Out-of-bounds write vulnerability in QTextCodec iconv-based encoding impacts Qt — Qt 1.9 Low 2026-10-27
CVE-2026-47486 NVIDIA PhysX 全平台越界写入漏洞 — PhysX 7.8 High 2026-10-27
CVE-2026-86577 Out-of-bounds Write Vulnerability in JP1 Products — JP1/Integrated Management 3 - Manager 9.4 Critical 2026-10-27
CVE-2026-116842 DevilutionX 1.4.0 through 1.5.5 Heap Buffer Overflow via libmpq__archive_dup — DevilutionX 6.1 Medium 2026-10-27
CVE-2026-116741 Speex through 1.2.1 Out-of-Bounds Write via speex_bits_read_whole_bytes — speex 6.5 Medium 2026-10-26
CVE-2026-116502 turboderp-org ExLlamaV2 GPTQ Index q_matrix.cu make_sequential out-of-bounds write — ExLlamaV2 4.4 Medium 2026-10-26
CVE-2026-116543 Open5GS 1.3.0 through 2.8.0 Heap Out-of-Bounds Write via SBI Multipart Parser — open5gs 7.5 High 2026-10-26
CVE-2026-116539 Netty netty-tcnative before 2.0.84.Final Heap Buffer Overflow via OpenSSL BIO — netty-tcnative 5.9 Medium 2026-10-26
CVE-2026-82945 Memory Corruption via FMMU Configuration Table Overflow — SOEM 6.5 Medium 2026-10-26
CVE-2026-82944 Buffer Overflow in CoE SDO Upload Multi-Segment Data Transfers — SOEM 8.8 High 2026-10-26
CVE-2026-107895 富士 V-SFT V7 文件越界写漏洞 — V-SFT 7.8 High 2026-10-26
CVE-2026-116099 Fusion Creators Studio SCP Containment Breach Multiplayer Skynet++ Virtual Machine BlitzBanks out-of-bounds write — SCP Containment Breach Multiplayer 6.3 Medium 2026-10-25
CVE-2026-116096 ggml-org llama.cpp Pocket-TTS pockettts-gen.cpp list_pockettts_state_slots out-of-bounds write — llama.cpp 5.3 Medium 2026-10-25
CVE-2026-79982 Out-of-bounds write in the USB Bluetooth HCI transport class when a controller-to-host HCI packet exceeds the bulk endpoint maximum packet size — zephyr 8.8 High 2026-10-23
CVE-2026-79978 Out-of-bounds write in the ADXL345 sensor driver RTIO streaming FIFO read path — zephyr 3.6 Low 2026-10-23
CVE-2026-115723 Snap7 through 1.4.3 Out-of-Bounds Write via BRecv and CheckAsBRecvCompletion — snap7 7.4 High 2026-10-23
CVE-2026-115504 CFITSIO through 4.7.0 Out-of-Bounds Write via ffgcls2 in getcols.c — cfitsio 7.8 High 2026-10-22
CVE-2026-115393 Wasmtime before 24.0.12, 25.0.0 before 36.0.13, 37.0.0 before 46.0.2, and 47.0.0 before 47.0.3 Cross-Engine Type Confusion — wasmtime 3.8 Low 2026-10-22
CVE-2026-111497 Out-of-Bounds Write in Google Brotli Decoder — Brotli 9.2 Critical 2026-10-22
CVE-2026-103634 Apache DataSketches: datasketches-cpp: Out-of-bounds read and write in Count-Min sketch deserialization allows memory corruption via a crafted sketch — Apache DataSketches - - 2026-10-22

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