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-55368 h2o: buffer overflow when using the %{error}x log directive — h2o 8.1 High 2026-11-04
CVE-2026-122127 CESNET ipfixcol2 2.7.1 before 2.9.0 Heap Buffer Overflow via TCP LZ4 Decoder — ipfixcol2 7.5 High 2026-11-04
CVE-2026-113780 ESF-IDF: Unvalidated Stack Pointer at the ESP-TEE Privilege-Switch Boundary — esp-idf 9.3 Critical 2026-11-04
CVE-2026-121962 FreeRDP before 3.32.2 Heap Buffer Overflow via Early User Authorization Read — FreeRDP 8.1 High 2026-11-04
CVE-2026-121954 FreeRDP before 3.32.2 Heap Out-of-Bounds Write in Planar Codec — FreeRDP 6.5 Medium 2026-11-04
CVE-2026-121952 FreeRDP before 3.32.2 Proxy Out-of-Bounds Write via Bitmap Cache v2 Capability — FreeRDP 9.8 Critical 2026-11-04
CVE-2026-100408 Git for Windows: git-credential-wincred Erase Path Heap Overflow — git 4.4 Medium 2026-11-04
CVE-2026-100407 Git for Windows: git-credential-wincred OAuth Store Heap Overflow — git 4.4 Medium 2026-11-04
CVE-2026-90634 Apache OpenOffice: Out-of-bounds write when importing encrypted PDF files — Apache OpenOffice - - 2026-11-04
CVE-2026-90629 Apache OpenOffice: Out of bounds memory access during WMF import — Apache OpenOffice - - 2026-11-04
CVE-2026-90626 Apache OpenOffice: Out-of-bounds write when importing encrypted PDF files — Apache OpenOffice - - 2026-11-04
CVE-2026-90624 Apache OpenOffice: PDF File Parsing Heap based Buffer-Overflow-Remote Code Execution Vulnerability — Apache OpenOffice - - 2026-11-04
CVE-2026-59268 Apache OpenOffice: Heap out-of-bounds write in WW8 PLCF reader — Apache OpenOffice - - 2026-11-04
CVE-2026-87039 I2S configure syscall handler passes an unvalidated user-supplied kernel object pointer to drivers — zephyr 7.8 High 2026-11-04
CVE-2026-80335 Out-of-bounds Write in Bootloader — Bootloader 8.4 High 2026-11-04
CVE-2026-121617 Linksys E5600 Header upload_fw.cgi init_multipart out-of-bounds write — E5600 7.5 High 2026-11-04
CVE-2026-121616 Linksys E5600 JSON Request mesh_login.cgi strcpy out-of-bounds write — E5600 5.3 Medium 2026-11-04
CVE-2026-84729 华硕路由器固件越界写漏洞 — Router firmware 7.2 High 2026-11-04
CVE-2026-114550 libwebsockets MQTT Protocol PUBACK Packet Handling Out-Of-Bounds Write Remote Code Execution Vulnerability — libwebsockets - - 2026-11-03
CVE-2026-120931 Chrome 156 以下 Android 版 WebGL 越界写入漏洞 — Chrome - - 2026-11-03
CVE-2026-121037 Chrome 157.0.8103.38 前 Windows 版 ANGLE 越界写漏洞 — Chrome - - 2026-11-03
CVE-2026-120959 MongoDB Atlas SQL ODBC Driver uses ignored SQLBindCol BufferLength as fixed-width row-array stride, causing out-of-bounds writes — Atlas SQL 3.7 Low 2026-11-03
CVE-2026-120952 MongoDB Atlas SQL ODBC Driver writes 48-byte Extended JSON into fixed 16-byte SQL_C_GUID target, causing a 32-byte out-of-bounds write — Atlas SQL ODBC Driver 7.1 High 2026-11-03
CVE-2026-61495 TinyUSB 0.21.0 Out-of-Bounds Write via mtp_container_get_string() — TinyUSB 6.8 Medium 2026-11-03
CVE-2026-40661 AMD Compressonator SDK 越界写漏洞 — AMD Compressionator SDK 5.2 Medium 2026-11-03
CVE-2026-121513 Out-of-bounds Write in µD3TN — µD3TN 7.5 High 2026-11-03
CVE-2026-121510 Out-of-bounds Write in µD3TN — µD3TN 7.5 High 2026-11-03
CVE-2026-121506 Out-of-bounds Write in NTPsec — NTPsec 7.4 High 2026-11-03
CVE-2026-85034 Out-of-bounds write in the Bluetooth GATT client: oversized notification and indication values delivered to subscribers — zephyr 6.7 Medium 2026-11-03
CVE-2026-120831 Libslirp: libslirp: queue pointer corruption in if_output() leading to denial of service — Red Hat Enterprise Linux 10 6.5 Medium 2026-11-03

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