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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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-25216 AnyBurn 4.3 Denial of Service Local Buffer Overflow — AnyBurn 6.2 Medium2026-03-26
CVE-2018-25215 Excel Password Recovery Professional 8.2.0.0 Local Buffer Overflow DoS — Excel Password Recovery Professional 5.5 Medium2026-03-26
CVE-2018-25213 Nsauditor 3.0.28.0 Local SEH Buffer Overflow — Nsauditor Local SEH Buffer Overflow 8.4 High2026-03-26
CVE-2018-25214 MegaPing Local Buffer Overflow Denial of Service — MegaPing 6.2 Medium2026-03-26
CVE-2018-25212 Boxoft wav-wma Converter 1.0 Local Buffer Overflow SEH — WAV to WMA Converter 8.4 High2026-03-26
CVE-2018-25211 Allok Video Splitter 3.1.1217 Buffer Overflow via License Name — Splitter 7.8 High2026-03-26
CVE-2019-25646 Tabs Mail Carrier 2.5.1 Buffer Overflow via MAIL FROM — Mail Carrier 9.8 Critical2026-03-24
CVE-2019-25644 WinMPG Video Convert 9.3.5 Buffer Overflow Local Denial of Service — WinMPG Video Convert Local Dos Exploit 6.2 Medium2026-03-24
CVE-2019-25637 X-NetStat Pro 5.63 Local Buffer Overflow via EggHunter — NetStat Pro 8.4 High2026-03-24
CVE-2019-25634 Base64 Decoder 1.1.2 Local Buffer Overflow SEH Egghunter — Base64 Decoder 8.4 High2026-03-24
CVE-2019-25633 AIDA64 Extreme 5.99.4900 SEH Buffer Overflow via EggHunter — AIDA64 Extreme 8.4 High2026-03-24
CVE-2019-25631 AIDA64 Business 5.99.4900 SEH Buffer Overflow via EggHunter — AIDA64 Business 8.4 High2026-03-24
CVE-2019-25629 AIDA64 Extreme 5.99.4900 SEH Buffer Overflow via Logging — AIDA64 Extreme 8.4 High2026-03-24
CVE-2019-25628 Download Accelerator Plus DAP 10.0.6.0 SEH Buffer Overflow — Download Accelerator Plus DAP 9.8 Critical2026-03-24
CVE-2026-4756 Out-of-bounds Write in MolotovCherry Android-ImageMagick7 — Android-ImageMagick7 7.8 High2026-03-24
CVE-2026-33854 Out-of-bounds Write in MolotovCherry Android-ImageMagick7 — Android-ImageMagick7 8.8 High2026-03-24
CVE-2026-33850 Out-of-bounds Write in WujekFoliarz DualSenseY-v2 — DualSenseY-v2 7.8 High2026-03-24
CVE-2026-4746 Heap Buffer Over-Write Vulenrabilty in timeplus-io/proton — proton 8.4 -2026-03-24
CVE-2019-25619 FTP Shell Server 6.83 Buffer Overflow via Account Name — FTP Shell Server 8.4 High2026-03-22
CVE-2019-25615 Lavavo CD Ripper 4.20 Local SEH Buffer Overflow — Lavavo CD Ripper 8.4 High2026-03-22
CVE-2019-25614 Free Float FTP 1.0 STOR Command Remote Buffer Overflow — Free Float FTP 9.8 Critical2026-03-22
CVE-2019-25612 Admin Express 1.2.5.485 Local SEH Buffer Overflow via Folder Path — Admin-Express 7.8 High2026-03-22
CVE-2019-25611 MiniFtp parseconf_load_setting Buffer Overflow via Configuration — MiniFtp 8.4 High2026-03-22
CVE-2019-25609 JetAudio jetCast Server 2.0 Local SEH Buffer Overflow — Server 8.4 High2026-03-22
CVE-2019-25607 Axessh 4.2 Local Stack-based Buffer Overflow via Log File Name — Axessh 8.4 High2026-03-22
CVE-2019-25606 Fast AVI MPEG Joiner 1.2.0812 Buffer Overflow Denial of Service — Fast AVI MPEG Joiner 5.5 Medium2026-03-22
CVE-2019-25604 DVDXPlayer Pro 5.5 Local Buffer Overflow with SEH — DVDXPlayer 8.4 High2026-03-22
CVE-2019-25603 TuneClone 2.20 Structured Exception Handler Buffer Overflow — TuneClone 8.4 High2026-03-22
CVE-2019-25601 UltraVNC Launcher 1.2.2.4 Denial of Service Buffer Overflow — UltraVNC Launcher 6.2 Medium2026-03-22
CVE-2019-25600 UltraVNC Viewer 1.2.2.4 Denial of Service via Buffer Overflow — UltraVNC Viewer 6.5 Medium2026-03-22

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