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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

2486 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-14612 Freeipa: ipa: idm: freeipa: off-by-one buffer overflows in ipa-otpd oauth2.c during oauth2 device authorization — Red Hat Enterprise Linux 10 4.2 Medium2026-07-03
CVE-2026-13053 WatchGuard Firebox Authenticated Out of Bounds Write in Management CLI Command Handler — Fireware OS--2026-07-02
CVE-2026-13050 WatchGuard Firebox networkd Out of Bounds Write Vulnerability — Fireware OS--2026-07-02
CVE-2026-13384 WatchGuard Firebox wgagent Out of Bounds Write Vulnerability — Fireware OS--2026-07-02
CVE-2026-13383 WatchGuard Firebox ikestubd Out of Bounds Write Vulnerability — Fireware OS--2026-07-02
CVE-2026-14392 Google Chrome 缓冲区错误漏洞 — Chrome--2026-07-01
CVE-2026-14395 Google Chrome 缓冲区错误漏洞 — Chrome--2026-07-01
CVE-2026-14400 Google Chrome 缓冲区错误漏洞 — Chrome--2026-07-01
CVE-2026-14397 Google Chrome 缓冲区错误漏洞 — Chrome--2026-07-01
CVE-2025-23351 NVIDIA BlueField 缓冲区错误漏洞 — BlueField GA 9.0 Critical2026-07-01
CVE-2025-23350 NVIDIA BlueField 缓冲区错误漏洞 — BlueField GA 9.0 Critical2026-07-01
CVE-2026-7840 UltraVNC repeater HTTP server global buffer overflow via long URI (pre-auth RCE) — UltraVNC 9.8 Critical2026-07-01
CVE-2026-7829 UltraVNC repeater authenticated out-of-bounds write in rule parser via oversized token — UltraVNC 7.2 High2026-07-01
CVE-2026-20461 MediaTek chipset 缓冲区错误漏洞 — MediaTek chipset--2026-07-01
CVE-2026-20458 MediaTek chipset 缓冲区错误漏洞 — MediaTek chipset--2026-07-01
CVE-2026-14191 WinRAR / UnRAR RAR5 recovery-volume (.rev) out-of-bounds heap write in RecVolumes5::ReadHeader — WinRAR 7.8 High2026-07-01
CVE-2026-14152 Google Chrome 缓冲区错误漏洞 — Chrome--2026-06-30
CVE-2026-13592 liftoff-sr CIPster EtherNet IP Message append out-of-bounds write — CIPster 7.3 High2026-06-29
CVE-2026-10644 Out-of-bounds write in Microchip SERCOM-G1 (PIC32CM-JH) async UART RX with 1-byte buffer — zephyr 4.2 Medium2026-06-28
CVE-2026-58049 FFmpeg - Out-of-Bounds Write in RASC Decoder decode_dlta() — FFmpeg 8.6 High2026-06-28
CVE-2026-10643 Out-of-bounds heap write in Zephyr `recvmsg()` ancillary-data path (`insert_pktinfo` undersizes the control-buffer capacity check) — zephyr 8.7 High2026-06-27
CVE-2026-57876 GV-LPC2011/LPC2211 - unauthorized out-of-bounds writing vulnerability (onvif.cgi) — GV-LPCLPC2011/2211 7.5 High2026-06-26
CVE-2026-6325 Out-of-bounds write in SetSuitesHashSigAlgo on oversized signature algorithms list — wolfSSL--2026-06-25
CVE-2026-6679 DTLS 1.3 ACK serialization heap buffer overflow via integer truncation — wolfSSL--2026-06-25
CVE-2026-6681 PKCS#7 decode ignores caller output buffer size, writing past buffer bounds — wolfSSL--2026-06-25
CVE-2026-55958 Renesas TSIP TLS 1.3 transcript buffer out-of-bounds write in tsip_StoreMessage — wolfSSL--2026-06-25
CVE-2026-56786 RTKLIB 2.4.3 - Out-of-bounds Write in decode_type1033 via Crafted RTCM3 Message — RTKLIB 9.8 Critical2026-06-25
CVE-2026-49839 jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow — jq 7.1 High2026-06-25
CVE-2026-55693 Vim: Out-of-bounds Write in Spell File Word Count — vim--2026-06-25
CVE-2026-55892 Vim: Out-of-bounds Write in Spell File Prefix Dump — vim 5.5 Medium2026-06-25

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