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-107441 Zyxel GS1900-24E 2.90 前 CGI 越界写漏洞 — GS1900-24E firmware 8.8 High 2026-11-03
CVE-2026-119739 Amlogic DroidLogic SubTitleService Out-of-Bounds Write via VobSub SET_CONTR — A95X 5.3 Medium 2026-11-02
CVE-2026-120058 psqlODBC row cache overflow when a later FETCH changes the column count — psqlODBC 7.5 High 2026-11-02
CVE-2026-115653 Cortex-M module ports save a preempted user-mode module thread's registers through its unchecked stack pointer in privileged mode — Eclipse ThreadX 7.0 High 2026-11-02
CVE-2026-120456 L-SMASH through 2.14.5 Heap Out-of-Bounds Write via hdlr and url Boxes — L-SMASH 6.1 Medium 2026-11-02
CVE-2026-120455 rapidyaml through 0.16.0 Out-of-Bounds Write via ParseEngine::_add_annotation() — rapidyaml 6.1 Medium 2026-11-02
CVE-2026-120451 libgphoto2 through 2.5.34 Buffer Overflow via jl2005c Camera Driver — libgphoto2 6.8 Medium 2026-11-02
CVE-2026-120452 libgphoto2 through 2.5.34 Heap Out-of-Bounds Read/Write via jl2005c Thumbnail Conversion — libgphoto2 5.4 Medium 2026-11-02
CVE-2026-120435 Netpbm before 10.86.51, 11.02.30, and 11.15.08 Heap Overflow in xpmtoppm — Netpbm 7.8 High 2026-11-02
CVE-2026-107457 Memory corruption vulnerability in QMqttClient impacts Qt MQTT — Qt 2.3 Low 2026-11-02
CVE-2026-68589 Modem 越界写入漏洞(MOLY01320076) — MediaTek chipset - - 2026-11-02
CVE-2026-20585 Modem 远程权限提升漏洞(越界写入) — MediaTek chipset - - 2026-11-02
CVE-2026-20584 Alps USB 驱动越界检查缺失导致内存破坏漏洞 — MediaTek chipset - - 2026-11-02
CVE-2026-20567 afe 越界写入漏洞:特权升级,无需交互 — MediaTek chipset - - 2026-11-02
CVE-2026-20566 Modem 越界写入漏洞:远程拒绝服务,需系统权限 — MediaTek chipset - - 2026-11-02
CVE-2026-20565 Modem 越界写入漏洞:权限提升风险 — MediaTek chipset - - 2026-11-02
CVE-2026-20564 Modem 越界写入漏洞,导致拒绝服务 — MediaTek chipset - - 2026-11-02
CVE-2026-20563 Modem 越界写入漏洞:远程拒绝服务 — MediaTek chipset - - 2026-11-02
CVE-2026-20557 Modem 越界写入漏洞:远程提权 — MediaTek chipset - - 2026-11-02
CVE-2026-20556 Modem 越界写入漏洞:远程提权,无需交互 — MediaTek chipset - - 2026-11-02
CVE-2026-20554 Modem 越界检查缺失致远程提权漏洞 — MediaTek chipset - - 2026-11-02
CVE-2026-20553 DA 越界写入漏洞:物理访问可提权 — MediaTek chipset - - 2026-11-02
CVE-2026-20552 ccci 存在越界写入漏洞,影响 MT6880 等芯片 — MediaTek chipset - - 2026-11-02
CVE-2026-20551 GNSS 越界写入漏洞:需用户交互的本地拒绝服务 — MediaTek chipset - - 2026-11-02
CVE-2026-20550 GNSS 越界写入漏洞,需用户交互,致拒绝服务 — MediaTek chipset - - 2026-11-02
CVE-2026-20549 Modem 越界写入漏洞:远程提权 — MediaTek chipset - - 2026-11-02
CVE-2026-20548 Modem 越界写入漏洞:远程提权,无需交互 — MediaTek chipset - - 2026-11-02
CVE-2026-20547 Modem 越界写漏洞:远程提权(补丁 MOLY01874018) — MediaTek chipset - - 2026-11-02
CVE-2026-20546 Modem 越界写入漏洞:远程提权 — MediaTek chipset - - 2026-11-02
CVE-2026-20545 Modem 越界写入漏洞致远程提权 — MediaTek chipset - - 2026-11-02

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