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-2020-7551 Schneider Electric Interactive Graphical SCADA System 缓冲区错误漏洞 — IGSS Definition (Def.exe) version 14.0.0.20247 7.8 -2020-11-19
CVE-2020-7563 多款Schneider Electric产品缓冲区错误漏洞 — Web Server on Modicon M340, Modicon Quantum and Modicon Premium Legacy offers and their Communication Modules (see notification for details) 8.8 -2020-11-18
CVE-2020-24436 Acrobat Pro DC PDF Export Out-Of-Bounds Write Vulnerability Could Lead to Arbitrary Code Execution — Acrobat Reader 7.8 High2020-11-05
CVE-2020-24411 Adobe Illustrator PDF File Parsing Out-Of-Bounds Write Vulnerability — Illustrator 7.8 High2020-10-20
CVE-2020-17416 Foxit Reader 缓冲区错误漏洞 — Reader 7.8 -2020-10-13
CVE-2020-17412 mPDF和Foxit PhantomPDF 缓冲区错误漏洞 — PhantomPDF 7.8 -2020-10-13
CVE-2020-1907 Facebook WhatsApp 缓冲区错误漏洞 — WhatsApp for Android 9.8 -2020-10-06
CVE-2020-7465 MPD 缓冲区错误漏洞 — MPD: FreeBSD PPP daemon 9.8 -2020-10-06
CVE-2020-8109 Bitdefender ace.xmd parser out-of-bounds write (VA-8772) — Bitdefender Engines 5.9 Medium2020-10-01
CVE-2020-15212 Out of bounds access in tensorflow-lite — tensorflow 8.1 High2020-09-25
CVE-2020-15214 Out of bounds write in tensorflow-lite — tensorflow 8.1 High2020-09-25
CVE-2020-14390 Linux kernel 缓冲区错误漏洞 — kernel 7.8 -2020-09-18
CVE-2020-14315 bsdiff 缓冲区错误漏洞 — bsdiff 9.8 -2020-09-16
CVE-2020-14386 Linux kernel 缓冲区错误漏洞 — kernel 6.7 Medium2020-09-16
CVE-2020-14331 Linux kernel 缓冲区错误漏洞 — Linux Kernel 6.6 -2020-09-15
CVE-2020-1912 Facebook Hermes 缓冲区错误漏洞 — Hermes 8.1 -2020-09-09
CVE-2020-1891 WhatsApp 缓冲区错误漏洞 — WhatsApp Android 9.8 -2020-09-03
CVE-2020-1894 WhatsApp 缓冲区错误漏洞 — WhatsApp Android 8.8 -2020-09-03
CVE-2020-7524 Schneider Electric Modicon M218 Logic Controller 缓冲区错误漏洞 — Modicon M218 Logic Controller V5.0.0.7 and prior 7.5 -2020-08-31
CVE-2020-3415 Cisco NX-OS Software Data Management Engine Remote Code Execution Vulnerability — Cisco NX-OS Software 8.8 -2020-08-27
CVE-2020-17404 Foxit Studio Photo 缓冲区错误漏洞 — Studio Photo 7.8 -2020-08-25
CVE-2020-17403 Foxit Studio Photo 缓冲区错误漏洞 — Studio Photo 7.8 -2020-08-25
CVE-2020-15629 Foxit Studio Photo 缓冲区错误漏洞 — Studio Photo 7.8 -2020-08-19
CVE-2020-16213 Advantech WebAccess HMI Designer 缓冲区错误漏洞 — Advantech WebAccess HMI Designer 7.8 -2020-08-06
CVE-2020-12011 Mitsubishi Electric MC Works64、MC Works32和ICONICS GENESIS64、GENESIS32 缓冲区错误漏洞 — Mitsubishi Electric MC Works64 9.8 -2020-07-16
CVE-2020-6089 LEAD Technologies LEADTOOLS 缓冲区错误漏洞 — Leadtools 7.8 -2020-07-01
CVE-2020-7502 Schneider Electric Modicon M218 Logic Controller 缓冲区错误漏洞 — Modicon M218 Logic Controller (Firmware version 4.3 and prior) 7.5 -2020-06-16
CVE-2020-10021 Out-of-bounds write in USB Mass Storage with unaligned sizes — zephyr 8.1 High2020-05-11
CVE-2020-10904 Foxit 3D Plugin 缓冲区错误漏洞 — PhantomPDF 7.8 -2020-04-22
CVE-2020-10897 Foxit 3D Plugin 缓冲区错误漏洞 — PhantomPDF 7.8 -2020-04-22

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