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 2231

2231 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-2023-45675 0 byte write heap buffer overflow in start_decoder in stb_vorbis — stb 6.5 Medium2023-10-20
CVE-2023-39431 Santesoft Sante DICOM Viewer Pro Out-of-bounds Write — Sante DICOM Viewer Pro 7.8 High2023-10-19
CVE-2023-44197 Junos OS and Junos OS Evolved: An rpd crash may occur when BGP is processing newly learned routes — Junos OS 7.5 High2023-10-12
CVE-2023-44178 Junos OS : Stack overflow vulnerability in CLI command processing — Junos OS 5.5 Medium2023-10-12
CVE-2023-44176 Junos OS : Stack overflow vulnerability in CLI command processing — Junos OS 5.5 Medium2023-10-12
CVE-2023-44177 Junos OS and Junos OS Evolved: Stack overflow vulnerability in CLI command processing — Junos OS 5.5 Medium2023-10-12
CVE-2023-43785 Libx11: out-of-bounds memory access in _xkbreadkeysyms() 6.5 Medium2023-10-10
CVE-2023-44083 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation V2201 7.8 High2023-10-10
CVE-2023-44082 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation V2201 7.8 High2023-10-10
CVE-2023-44081 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation V2201 7.8 High2023-10-10
CVE-2023-43641 libcue vulnerable to out-of-bounds array access — libcue 8.8 High2023-10-09
CVE-2023-3024 Bluetooth LE segmented 'prepare write response' packet may lead to out-of-bounds memory access — GSDK 5.9 Medium2023-09-29
CVE-2023-40307 Privileges Memory Corruption (Out-of-bound write) — SAP Privileges 6.3 Medium2023-09-28
CVE-2023-20109 Cisco IOS 缓冲区错误漏洞 — IOS 6.6 Medium2023-09-27
CVE-2023-42753 Kernel: netfilter: potential slab-out-of-bound access due to integer underflow — Red Hat Enterprise Linux 7 7.0 High2023-09-25
CVE-2023-40163 Accusoft ImageGear 缓冲区错误漏洞 — ImageGear 9.8 Critical2023-09-25
CVE-2023-5068 Delta Electronics DIAScreen Out-of-bounds Write — DIAScreen 7.8 High2023-09-21
CVE-2023-42443 Vyper vulnerable to memory corruption in certain builtins utilizing `msize` — vyper 8.1 High2023-09-18
CVE-2023-40018 FreeSWITCH allows remote users to trigger out of bounds write by offering an ICE candidate with unknown component ID — freeswitch 7.5 High2023-09-15
CVE-2023-3935 Wibu: Buffer Overflow in CodeMeter Runtime — CodeMeter Runtime 9.8 Critical2023-09-13
CVE-2023-26369 [Google Project Zero] Adobe Acrobat DC OOBW 0-day actively exploited in the wild — Acrobat Reader 7.8 High2023-09-13
CVE-2023-41033 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V35.0 7.8 High2023-09-12
CVE-2023-41032 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-09-12
CVE-2023-38072 Siemens JT2GO 缓冲区错误漏洞 — JT2Go 7.8 High2023-09-12
CVE-2023-40308 Memory Corruption vulnerability in SAP CommonCryptoLib — SAP CommonCryptoLib 7.5 High2023-09-12
CVE-2022-28834 Adobe InCopy Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InCopy 7.8 High2023-09-11
CVE-2022-28836 Adobe InCopy Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InCopy 7.8 High2023-09-11
CVE-2022-28831 Adobe InDesign Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InDesign Desktop 7.8 High2023-09-11
CVE-2022-28833 Adobe InDesign Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InDesign Desktop 7.8 High2023-09-11
CVE-2023-30800 MikroTik RouterOS Web Interface Heap Corruption — RouterOS 7.5 High2023-09-07

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