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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

2488 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-59087 Gimp: heap buffer overflow in `file-seattle-filmworks` load — `fread` writes attacker-controlled length into undersized allocation — Red Hat Enterprise Linux 6 7.8 High2026-08-10
CVE-2026-19387 Gstreamer: gstreamer1-plugins-bad-free: gstreamer: heap out-of-bounds write in adpcmdec ima/dvi adpcm decoder — Red Hat Enterprise Linux 10 7.6 High2026-08-10
CVE-2026-54212 TeamDavid: Buffer Overflow in JSON-parsing — TeamDavid 9.5 Critical2026-08-07
CVE-2026-54211 TeamDavid: Buffer Overflow in multiple form data parameters — TeamDavid 9.5 Critical2026-08-07
CVE-2026-54210 TeamDavid: Buffer Overflow in file names of file upload functionalities — TeamDavid 9.5 Critical2026-08-07
CVE-2026-17264 Medixant RadiAnt DICOM Out-of-bounds write — RadiAnt DICOM 4.3 Medium2026-08-06
CVE-2026-70632 FFmpeg 4.4 < 9.0 Heap Out-of-Bounds Write in CFHD Decoder via AVI Demuxing — FFmpeg 7.8 High2026-08-06
CVE-2026-19173 Google Chrome 缓冲区错误漏洞 — Chrome--2026-08-06
CVE-2026-19162 Chrome 151.0.7922.109前越界写漏洞 — Chrome--2026-08-06
CVE-2026-19148 Google Chrome 缓冲区错误漏洞 — Chrome--2026-08-06
CVE-2026-19157 Google Chrome 缓冲区错误漏洞 — Chrome--2026-08-06
CVE-2026-5857 Contiki-NG MQTT Client Out-of-Bounds Write in PUBLISH Topic Parser via Persistent State Between TCP Segments — Contiki-NG 8.1 High2026-08-06
CVE-2026-8325 PDF File Parsing Out-of-Bounds Write Vulnerability in Autodesk Revit — Revit 7.8 High2026-08-06
CVE-2026-43629 llama.cpp b4882–b9058 Buffer Overflow in KV Cache State Restore — llama.cpp 8.1 High2026-08-06
CVE-2026-71263 FreeModbus LINUXTCP Port Off-by-One Global Buffer Overflow in xMBPortTCPPool() — FreeModbus 9.1 Critical2026-08-05
CVE-2026-71255 nanoMODBUS Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res() — nanoMODBUS 8.6 High2026-08-05
CVE-2026-71254 nanoMODBUS Server-Side Out-of-Bounds Write in handle_read_file_record() — nanoMODBUS 9.8 Critical2026-08-05
CVE-2026-24253 NVIDIA Dynamo 缓冲区错误漏洞 — Dynamo 8.2 High2026-08-04
CVE-2026-18739 Popt-devel: popt-static: off-by-one in poptstuffargs — popt 2.5 Low2026-08-04
CVE-2026-20493 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20491 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20485 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20481 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20497 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20478 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20477 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20476 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20475 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20472 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20471 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset--2026-08-03

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