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-20499 Modem 越界写入漏洞:远程提权风险 — MediaTek chipset - - 2026-11-02
CVE-2026-119777 Gstreamer1-plugins-bad-free: gstreamer1-plugins-bad-free: stack buffer overflow in h.266/vvc parser — Red Hat Enterprise Linux 10 8.8 High 2026-10-30
CVE-2026-104067 Scribus before 1.6.7 and 1.7.x before 1.7.4 Out-of-Bounds Memory Access via SVM Import Plugin — Scribus 7.8 High 2026-10-30
CVE-2026-104066 Scribus before 1.6.7 and 1.7.x before 1.7.4 Heap Buffer Overflow via PICT 4-bit Pixel Unpacking — Scribus 7.8 High 2026-10-30
CVE-2026-104065 Scribus before 1.6.7 and 1.7.x before 1.7.4 Heap Out-of-Bounds Write via Micrografx Draw Import — Scribus 7.8 High 2026-10-30
CVE-2026-104062 Scribus before 1.6.7 and 1.7.x before 1.7.4 Heap Buffer Overflow via PICT Pixmap Loader — Scribus 7.8 High 2026-10-30
CVE-2026-104061 Scribus before 1.6.7 and 1.7.x before 1.7.4 Heap Out-of-Bounds Write via PSD Image Loader — Scribus 7.8 High 2026-10-30
CVE-2026-61626 libass: Out-of-bounds bit clears for negative Matroska ReadOrder values — libass 7.3 High 2026-10-30
CVE-2026-111487 Out-of-bounds write vulnerability in the assimp scene import plugin of Qt3D impacts Qt Framework — Qt Framework 4.3 Medium 2026-10-30
CVE-2026-119601 AFFLIB through 3.7.22 Heap Out-of-Bounds Write in af_get_page — AFFLIB 6.1 Medium 2026-10-30
CVE-2026-119379 SQLite before 3.54.0 Heap Buffer Overflow via Session Extension sessionUpdateFind() — SQLite 7.8 High 2026-10-30
CVE-2026-119374 SQLite before 3.54.0 Heap Buffer Overflow via FTS5 fts5DoSecureDelete() — SQLite 7.8 High 2026-10-30
CVE-2026-119373 SQLite before 3.54.0 FTS5 Heap Buffer Overflow via fts5MergeRowidLists() — SQLite 7.8 High 2026-10-30
CVE-2026-115455 Gcc: stack overflow in std::bitset on libstdc++ — Red Hat Hardened Images 6.5 Medium 2026-10-30
CVE-2026-114690 Gcc: confirmed out-of-bounds read/write in libstdc++ parallel `std — Red Hat Enterprise Linux 10 6.2 Medium 2026-10-30
CVE-2026-65587 GPU DDK - OOB write in CalculateNPOTTwiddleSparsePageMap via TEXTURE_BASE_LEVEL change — Graphics DDK - - 2026-10-30
CVE-2026-119262 Chrome 156 前 V8 输入验证漏洞可致远程代码执行 — Chrome - - 2026-10-30
CVE-2026-8824 VTK 9.6.1 vtkBMPReader 缓冲区溢出漏洞 — vtk 7.5 High 2026-10-29
CVE-2026-8822 VTK 9.6.1 vtkDEMReader 内存破坏漏洞 — vtk 7.5 High 2026-10-29
CVE-2026-118673 KeePassXC: Out-of-bounds write in browser integration response encryption with oversized database responses — keepassxc 4.1 Medium 2026-10-29
CVE-2026-111732 Out-of-bounds write when parsing AR Vendor Block requests — P-Net 9.3 Critical 2026-10-29
CVE-2026-111730 Out-of-bounds write in CheckPeers block parser due to unvalidated peer station name length — P-Net 7.2 High 2026-10-29
CVE-2026-93011 Dnsmasq: dnsmasq: heap out-of-bounds write in dnssec validator via to_wire/from_wire transforms — Red Hat Ceph Storage 9 5.3 Medium 2026-10-29
CVE-2026-118753 FreeImage through 3.18.0 and danoli3 fork before 3.19.25 Heap Buffer Overflow via GIF_PLAYBACK Compositing — FreeImage 7.8 High 2026-10-28
CVE-2026-118752 FreeImage through 3.18.0 and danoli3 fork before 3.19.22 Heap Buffer Overflow via IFF/LBM PBM RLE Decoder — FreeImage 7.8 High 2026-10-28
CVE-2026-58458 Don't Starve Together Memory Corruption via world_gen_data — Don't Starve Together 6.5 Medium 2026-10-28
CVE-2026-82962 Out-of-bounds write in Zephyr Ethernet L2 when adding the link-layer header to a forwarded packet — zephyr 6.5 Medium 2026-10-28
CVE-2026-82961 Unvalidated pin index in GPIO syscall handlers allows out-of-bounds kernel writes from user mode — zephyr 7.8 High 2026-10-28
CVE-2026-103392 Session Smart Router: A SACK option causes out-of-bounds memory access and TCP payload corruption when TCP sequence stitching is enabled — Session Smart Router 4.8 Medium 2026-10-28
CVE-2026-103391 Session Smart Router: An attacker-controlled TCP option causes an out-of-bounds write when using the TCP proxy feature — Session Smart Router 5.3 Medium 2026-10-28

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