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 2228

2228 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-2024-20726 [TianfuCup] JP2K Image Parsing Out-Of-Bounds Write — Acrobat Reader 7.8 High2024-02-15
CVE-2024-20727 [TianfuCup] out-of-bounds access vulnerability when parsing jpeg2000 — Acrobat Reader 7.8 High2024-02-15
CVE-2024-20728 ZDI-CAN-22727: Adobe Acrobat Pro DC Annotation Out-Of-Bounds Write Remote Code Execution Vulnerability — Acrobat Reader 7.8 High2024-02-15
CVE-2024-20744 Adobe Substance 3D Paint PICT Parsing Access Violation Write Vulnerability — Substance3D - Painter 7.8 High2024-02-15
CVE-2024-20743 Adobe Substance 3D Paint PSD Parsing Out-Of-Bounds Write Vulnerability — Substance3D - Painter 7.8 High2024-02-15
CVE-2024-20740 Adobe Substance 3D Paint PSD Parsing Out-Of-Bounds Write Vulnerability — Substance3D - Painter 7.8 High2024-02-15
CVE-2023-48229 Out-of-bounds write in the radio driver for Contiki-NG nRF platforms — contiki-ng 7.0 High2024-02-14
CVE-2024-24924 Siemens Simcenter Femap 缓冲区错误漏洞 — Simcenter Femap 7.8 High2024-02-13
CVE-2024-24922 Siemens Simcenter Femap 缓冲区错误漏洞 — Simcenter Femap 7.8 High2024-02-13
CVE-2024-24920 Siemens Simcenter Femap 缓冲区错误漏洞 — Simcenter Femap 7.8 High2024-02-13
CVE-2024-23803 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation V2201 7.8 High2024-02-13
CVE-2024-23795 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation V2201 7.8 High2024-02-13
CVE-2024-21762 Fortinet FortiOS 缓冲区错误漏洞 — FortiProxy 9.6 Critical2024-02-09
CVE-2024-0229 Xorg-x11-server: reattaching to different master device may lead to out-of-bounds memory access 7.8 High2024-02-09
CVE-2024-0244 Canon 多款产品缓冲区错误漏洞 — Satera MF750C Series 9.8 Critical2024-02-06
CVE-2023-6234 Canon 多款产品缓冲区错误漏洞 — Satera LBP670C Series 9.8 Critical2024-02-06
CVE-2023-6233 Canon 多款产品缓冲区错误漏洞 — Satera LBP670C Series 9.8 Critical2024-02-06
CVE-2023-6232 Canon 多款产品缓冲区错误漏洞 — Satera LBP670C Series 9.8 Critical2024-02-06
CVE-2023-6231 Canon 多款产品缓冲区错误漏洞 — Satera LBP670C Series 9.8 Critical2024-02-06
CVE-2023-6230 Canon 多款产品缓冲区错误漏洞 — Satera LBP670C Series 9.8 Critical2024-02-06
CVE-2023-6229 Canon多款产品缓冲区错误漏洞 — Satera LBP670C Series 9.8 Critical2024-02-06
CVE-2023-5643 Mali GPU Kernel Driver allows improper GPU memory processing operations — Bifrost GPU Kernel Driver 7.8 -2024-02-05
CVE-2023-6387 Incorrect buffer parsing in Bluetooth LE sample code may lead to buffer overflow — GSDK 7.5 High2024-02-02
CVE-2023-45734 Dsoftbus has an out-of-bounds write vulnerability — OpenHarmony 4.2 Medium2024-02-02
CVE-2023-40548 Shim: interger overflow leads to heap buffer overflow in verify_sbat_section on 32-bits systems — Red Hat Enterprise Linux 7 7.4 High2024-01-29
CVE-2023-52355 Libtiff: tiffrasterscanlinesize64 produce too-big size and could cause oom 7.5 High2024-01-25
CVE-2023-40547 Shim: rce in http boot support may lead to secure boot bypass — Red Hat Enterprise Linux 7 8.3 High2024-01-25
CVE-2024-0409 Xorg-x11-server: selinux context corruption 7.8 High2024-01-18
CVE-2023-6816 Xorg-x11-server: heap buffer overflow in devicefocusevent and procxiquerypointer — Red Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSION 9.8 Critical2024-01-18
CVE-2024-0646 Kernel: ktls overwrites readonly memory pages when using function splice with a ktls socket as destination 7.0 High2024-01-17

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