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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2200 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-2923 GStreamer DVB Subtitles Out-Of-Bounds Write Remote Code Execution Vulnerability — GStreamer 8.4 -2026-03-13
CVE-2026-2922 GStreamer RealMedia Demuxer Out-Of-Bounds Write Remote Code Execution Vulnerability — GStreamer 8.4 -2026-03-13
CVE-2026-29775 FreeRDP has a heap-buffer-overflow in bitmap_cache_put via OOB cacheId — FreeRDP 5.3 Medium2026-03-13
CVE-2026-29774 FreeRDP has a heap-buffer-overflow in avc420_yuv_to_rgb via OOB regionRects — FreeRDP 5.3 Medium2026-03-13
CVE-2026-0957 Out-Of-Bounds Write in Digilent DASYLab — DASYLab 7.8 High2026-03-13
CVE-2026-0954 Out-Of-Bounds Write When Opening a Corrupt DSB File in Digilent DASYLab — DASYLab 7.8 High2026-03-13
CVE-2026-3909 Google Chrome 缓冲区错误漏洞 — Chrome 8.8 -2026-03-12
CVE-2026-4016 GPAC SVG Parser load_svg.c svgin_process out-of-bounds write — GPAC 5.3 Medium2026-03-12
CVE-2026-27703 RIOT has an Out-of-Bounds Write in nanoCoAP Handler — RIOT 7.5 High2026-03-11
CVE-2019-25484 WinMPG iPod Convert 3.0 Register Field Buffer Overflow DoS — WinMPG iPod Convert 6.2 Medium2026-03-11
CVE-2019-25485 R 3.4.4 Windows x64 Buffer Overflow SEH DEP ASLR Bypass — R 6.2 Medium2026-03-11
CVE-2019-25478 GetGo Download Manager 6.2.2.3300 Buffer Overflow DoS — GetGo Download Manager 7.5 High2026-03-11
CVE-2019-25477 RAR Password Recovery 1.80 Denial of Service Buffer Overflow — RAR Password Recovery 6.2 Medium2026-03-11
CVE-2019-25476 Outlook Password Recovery 2.10 Denial of Service Buffer Overflow — Outlook Password Recovery Denial of Service Exploit 6.2 Medium2026-03-11
CVE-2019-25475 SQL Server Password Changer 1.90 Denial of Service Buffer Overflow — SQL Server Password Changer Denial of Service Exploit 6.2 Medium2026-03-11
CVE-2019-25474 Easy MP3 Downloader 4.7.8.8 Denial of Service Buffer Overflow — Easy MP3 Downloader Denial of Service 6.2 Medium2026-03-11
CVE-2019-25469 Folder Lock 7.7.9 Denial of Service via Serial Number Field — Folder Lock 6.2 Medium2026-03-11
CVE-2019-25467 Verypdf docPrint Pro 8.0 Local SEH Buffer Overflow — docPrint Pro 8.4 High2026-03-11
CVE-2019-25466 Easy File Sharing Web Server 7.2 Local SEH Overflow — Easy File Sharing Web Server 8.4 High2026-03-11
CVE-2019-25463 SpotIE Internet Explorer Password Recovery 2.9.5 Key Field DoS — SpotIE Internet Explorer Password Recovery 6.2 Medium2026-03-11
CVE-2026-21362 Illustrator | Out-of-bounds Write (CWE-787) — Illustrator 7.8 High2026-03-10
CVE-2026-27272 Illustrator | Out-of-bounds Write (CWE-787) — Illustrator 7.8 High2026-03-10
CVE-2026-27274 Substance3D - Stager | Out-of-bounds Write (CWE-787) — Substance3D - Stager 7.8 High2026-03-10
CVE-2026-27273 Substance3D - Stager | Out-of-bounds Write (CWE-787) — Substance3D - Stager 7.8 High2026-03-10
CVE-2026-27275 Substance3D - Stager | Out-of-bounds Write (CWE-787) — Substance3D - Stager 7.8 High2026-03-10
CVE-2026-27279 Substance3D - Stager | Out-of-bounds Write (CWE-787) — Substance3D - Stager 7.8 High2026-03-10
CVE-2026-27280 DNG SDK | Out-of-bounds Write (CWE-787) — DNG SDK 7.8 High2026-03-10
CVE-2026-25569 Siemens SICAM SIAPP SDK 缓冲区错误漏洞 — SICAM SIAPP SDK 7.4 High2026-03-10
CVE-2026-3038 Local DoS and possible privilege escalation via routing sockets — FreeBSD 6.2AIMediumAI2026-03-09
CVE-2025-41766 Stack buffer overflow on parsing web request — UBR-01 Mk II 8.8 High2026-03-09

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