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-2018-25223 Crashmail 1.6 Stack-based Buffer Overflow Remote Code Execution — Crashmail 9.8 Critical2026-03-28
CVE-2018-25222 SC v7.16 Stack-Based Buffer Overflow Remote Code Execution — SC 8.4 High2026-03-28
CVE-2018-25221 EChat Server 3.1 Buffer Overflow via chat.ghp username Parameter — EChat Server 9.8 Critical2026-03-28
CVE-2018-25220 Bochs 2.6-5 Buffer Overflow Remote Code Execution — BOCHS 9.8 Critical2026-03-28
CVE-2017-20229 MAWK 1.3.3-17 Stack-Based Buffer Overflow — MAWK 9.8 Critical2026-03-28
CVE-2017-20227 JAD 1.5.8e-1kali1 Stack-Based Buffer Overflow — JAD Java Decompiler 9.8 Critical2026-03-28
CVE-2017-20226 Mapscrn 2.0.3 Stack-Based Buffer Overflow — Mapscrn 8.4 High2026-03-28
CVE-2017-20225 TiEmu 2.08 Stack-Based Buffer Overflow Vulnerability — TiEmu 9.8 Critical2026-03-28
CVE-2016-20049 JAD 1.5.8e-1kali1 Stack-Based Buffer Overflow Remote Code Execution — JAD Java Decompiler 9.8 Critical2026-03-28
CVE-2016-20047 EKG Gadu 1.9 Local Buffer Overflow via Username Parameter — EKG Gadu 8.4 High2026-03-28
CVE-2016-20046 zFTP Client 20061220+dfsg3-4.1 Local Buffer Overflow — zFTP Client 8.4 High2026-03-28
CVE-2016-20044 PInfo 0.6.9-5.1 Local Buffer Overflow via -m Parameter — PInfo 8.4 High2026-03-28
CVE-2016-20045 HNB Organizer 1.9.18-10 Local Buffer Overflow via -rc Parameter — HNB 8.4 High2026-03-28
CVE-2016-20043 NRSS RSS Reader 0.3.9-1 Stack Buffer Overflow — NRSS Reader 8.4 High2026-03-28
CVE-2016-20042 TRN 3.6-23 Stack Buffer Overflow Local Code Execution — Threaded USENET News Reader 8.4 High2026-03-28
CVE-2016-20038 yTree 1.94-1.1 Stack-Based Buffer Overflow — yTree 8.4 High2026-03-28
CVE-2016-20039 Multi Emulator Super System 0.154-3.1 Buffer Overflow — Mess Emulator 8.4 High2026-03-28
CVE-2016-20037 xwpe 1.5.30a-2.1 Stack-based Buffer Overflow — xWPE 8.4 High2026-03-28
CVE-2026-33721 MapServer has heap buffer overflow in SLD `Categorize` Threshold parsing — MapServer 5.3 Medium2026-03-27
CVE-2026-33536 ImageMagick has an Out-of-bounds Write via InterpretImageFilename — ImageMagick 5.1 Medium2026-03-26
CVE-2026-33535 ImageMagick has an Out-of-Bounds write of a zero byte in its X11 display interaction — ImageMagick 4.0 Medium2026-03-26
CVE-2026-27816 EVerest's ISO15118 update_energy_transfer_modes overflow can corrupt EVSE state — everest-core 8.2 -2026-03-26
CVE-2026-27815 EVerest: ISO15118 session_setup payment options overflow can corrupt EVSE state — everest-core 8.2 -2026-03-26
CVE-2026-27664 Siemens多款产品 缓冲区错误漏洞 — CPCI85 Central Processing/Communication 7.5 High2026-03-26
CVE-2019-25650 River Past CamDo 3.7.6 Structured Exception Handler Buffer Overflow — River Past CamDo 8.4 High2026-03-26
CVE-2019-25649 River Past Audio Converter 7.7.16 Local Buffer Overflow DoS — River Past Audio Converter 5.5 Medium2026-03-26
CVE-2019-25648 MyVideoConverter Pro 3.14 Denial of Service Buffer Overflow — MyVideoConverter Pro 6.2 Medium2026-03-26
CVE-2018-25219 PassFab Excel Password Recovery 8.3.1 SEH Buffer Overflow — Excel Password Recovery 8.4 High2026-03-26
CVE-2018-25218 PassFab RAR Password Recovery 9.3.2 SEH Buffer Overflow — RAR Password Recovery 8.4 High2026-03-26
CVE-2018-25217 PDF Explorer 1.5.66.2 Structured Exception Handler Local Code Execution — PDF Explorer 8.4 High2026-03-26

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