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-2025-20646 MediaTek Chipsets 缓冲区错误漏洞 — MT6890, MT7915, MT7916, MT7981, MT7986 9.8 -2025-03-03
CVE-2025-20645 MediaTek Chipsets 缓冲区错误漏洞 — MT6765, MT6768, MT6833, MT6835, MT6853, MT6855, MT6879, MT6886, MT6893, MT6897, MT6983, MT6985, MT6989, MT8796 6.7 -2025-03-03
CVE-2025-1744 Out-of-bounds Write in radare2 — radare2 7.8 -2025-02-28
CVE-2025-0236 Canon多款产品 缓冲区错误漏洞 — Generic PCL6 V4 Printer Driver 5.3 Medium2025-02-26
CVE-2025-0235 Canon多款产品 缓冲区错误漏洞 — Generic PCL6 V4 Printer Driver 5.3 Medium2025-02-26
CVE-2025-0234 Canon多款产品 缓冲区错误漏洞 — Generic PCL6 V4 Printer Driver 5.3 Medium2025-02-26
CVE-2025-26598 Xorg: xwayland: out-of-bounds write in createpointerbarrierclient() 7.8 High2025-02-25
CVE-2025-26596 Xorg: xwayland: heap overflow in xkbwritekeysyms() 7.8 High2025-02-25
CVE-2025-0690 Grub2: read: integer overflow may lead to out-of-bounds write 6.1 Medium2025-02-24
CVE-2025-27105 AugAssign evaluation order causing OOB write within the object in Vyper — vyper 6.5 -2025-02-21
CVE-2025-1471 Eclipse OMR: Buffer overflow vulnerability — Eclipse OMR 9.8 -2025-02-21
CVE-2025-0677 Grub2: ufs: integer overflow may lead to heap based out-of-bounds write when handling symlinks 6.4 Medium2025-02-19
CVE-2025-0624 Grub2: net: out-of-bounds write in grub_net_search_config_file() 7.6 High2025-02-19
CVE-2024-45777 Grub2: grub-core/gettext: integer overflow leads to heap oob write. 6.7 Medium2025-02-19
CVE-2024-45781 Grub2: fs/ufs: oob write in the heap 6.7 Medium2025-02-18
CVE-2024-45776 Grub2: grub-core/gettext: integer overflow leads to heap oob write and read. 6.7 Medium2025-02-18
CVE-2024-45774 Grub2: reader/jpeg: heap oob write during jpeg parsing 6.7 Medium2025-02-18
CVE-2024-45320 Fujifilm DocuPrint多款产品 缓冲区错误漏洞 — DocuPrint CP225w 6.2 -2025-02-18
CVE-2025-26508 Certain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed Printers – Potential Remote Code Execution and Potential Elevation of Privilege — Certain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed Printers 9.8 -2025-02-14
CVE-2025-26519 musl libc 安全漏洞 — musl 8.1 High2025-02-14
CVE-2024-11345 Heap-based memory vulnerability in the Postscript interpreter in various Lexmark devices — CX, XC, CS, MS, MX, XM, et. al. 7.3 High2025-02-13
CVE-2024-0143 NVIDIA nvJPEG2000 安全漏洞 — nvJPEG2000 6.8 Medium2025-02-12
CVE-2024-0142 NVIDIA nvJPEG2000 缓冲区错误漏洞 — nvJPEG2000 6.8 Medium2025-02-12
CVE-2025-1240 WinZip 7Z File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — WinZip 7.8 -2025-02-11
CVE-2025-0910 PDF-XChange Editor U3D File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — PDF-XChange Editor 7.8 -2025-02-11
CVE-2024-12547 Tungsten Automation Power PDF JPF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — Power PDF 7.8 -2025-02-11
CVE-2025-21161 Substance3D - Designer | Out-of-bounds Write (CWE-787) — Substance3D - Designer 7.8 High2025-02-11
CVE-2025-21157 InDesign Desktop | Out-of-bounds Write (CWE-787) — InDesign Desktop 7.8 High2025-02-11
CVE-2025-21121 InDesign Desktop | Out-of-bounds Write (CWE-787) — InDesign Desktop 7.8 High2025-02-11
CVE-2024-57961 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.8 Medium2025-02-06

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