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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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-3812 Kernel: tun: bugs for oversize packet when napi frags enabled in tun_napi_alloc_frags — Red Hat Enterprise Linux 8 7.8 High2023-07-24
CVE-2023-3611 Out-of-bounds write in Linux kernel's net/sched: sch_qfq component — Kernel 7.8 High2023-07-21
CVE-2021-39822 Adobe InDesign BMP File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InDesign 7.8 High2023-07-20
CVE-2023-3633 Out of Bounds Memory Corruption Issue in CEVA Engine — Engines 8.1 High2023-07-14
CVE-2023-25078 DoS due to heap overflow — Experion Server 9.8 Critical2023-07-13
CVE-2023-23585 Server DoS due to heap overflow — Experion Server 9.8 Critical2023-07-13
CVE-2023-29308 [FG-VD-23-009] Adobe InDesign 2023 Arbitrary Code Execution Vulnerability Notification — InDesign 7.8 High2023-07-12
CVE-2023-3596 Rockwell Automation Allen-Bradley ControlLogix Communication Modules vulnerable to Denial of Service — 1756-EN4TR Series A 7.5 High2023-07-12
CVE-2023-3595 Rockwell Automation ControlLogix Communication Modules Vulnerable to Remote Code Execution — 1756-EN2T Series A, B, C 9.8 Critical2023-07-12
CVE-2023-2072 Rockwell Automation PowerMonitor 1000 Cross-Site Scripting Vulnerability — PowerMonitor 1000 8.8 High2023-07-11
CVE-2023-37248 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation V2201 7.8 High2023-07-11
CVE-2023-35871 Memory Corruption vulnerability in SAP Web Dispatcher — SAP Web Dispatcher 7.7 High2023-07-11
CVE-2023-35001 Linux Kernel nftables Out-Of-Bounds Read/Write Vulnerability — Linux Kernel 7.8 High2023-07-05
CVE-2023-3090 Out-of-bounds write in Linux kernel's ipvlan network driver — Kernel 7.8 High2023-06-28
CVE-2023-2290 Lenovo ThinkPad 安全漏洞 — ThinkPad 6.4 Medium2023-06-26
CVE-2023-28064 Dell BIOS 缓冲区错误漏洞 — CPG BIOS 3.5 Low2023-06-23
CVE-2023-3110 Buffer overflow in S0 Decryption on Unify Gateway — Unify Gateway 9.6 Critical2023-06-21
CVE-2023-0972 Buffer overflow in S0 Decryption on Z/IP Gatweay — Z/IP Gateway 9.6 Critical2023-06-21
CVE-2023-0970 Serial API Buffer Overflow in Z/IP Gateway — Z/IP Gateway 7.1 High2023-06-21
CVE-2023-2569 Schneider Electric EcoStruxure Foxboro DCS 缓冲区错误漏洞 — EcoStruxure Foxboro DCS Control Core Services 7.8 High2023-06-14
CVE-2023-22639 Fortinet FortiOS 缓冲区错误漏洞 — FortiOS 6.3 Medium2023-06-13
CVE-2023-32203 Horner Automation Cscape Out-of-bounds Write — Cscape 7.8 High2023-06-06
CVE-2023-32539 Horner Automation Cscape Out-of-bounds Write — Cscape 7.8 High2023-06-06
CVE-2022-48188 Lenovo Desktops和ThinkStation 缓冲区错误漏洞 — ThinkStation BIOS 6.7 Medium2023-06-05
CVE-2022-48181 Lenovo ThinkPad 缓冲区错误漏洞 — ThinkStation BIOS 6.7 Medium2023-06-05
CVE-2023-2687 Silicon Labs Gecko SDK 安全漏洞 — Gecko SDK 2.9 Low2023-06-02
CVE-2023-25537 Dell PowerEdge Server BIOS 缓冲区错误漏洞 — PowerEdge Platform 6.1 Medium2023-05-22
CVE-2022-47390 CODESYS: Multiple products prone to stack based out-of-bounds write — CODESYS Control RTE (SL) 8.8 High2023-05-15
CVE-2022-47389 CODESYS: Multiple products prone to stack based out-of-bounds write — CODESYS Control RTE (SL) 8.8 High2023-05-15
CVE-2022-47388 CODESYS: Multiple products prone to stack based out-of-bounds write — CODESYS Control RTE (SL) 8.8 High2023-05-15

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