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-2022-42378 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42380 Tracker Software PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42381 Tracker Software PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42382 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42394 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42395 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42400 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42410 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42415 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42416 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42419 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42420 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42421 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42423 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2023-23609 contiki-ng BLE-L2CAP contains Improper size validation of L2CAP frames — contiki-ng 8.2 High2023-01-25
CVE-2022-41989 CVE-2022-41989 — RTLS Studio 9.0 Critical2023-01-18
CVE-2023-21606 Adobe Acrobat Reader DC Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — Acrobat Reader 7.8 High2023-01-18
CVE-2023-21609 Adobe Acrobat Reader DC AcroForm Annotation Out-Of-Bounds Write Remote Code Execution Vulnerability — Acrobat Reader 7.8 High2023-01-18
CVE-2006-20001 Apache HTTP Server: mod_dav out of bounds read, or write of zero byte — Apache HTTP Server 7.5 -2023-01-17
CVE-2022-3087 Fuji Electric Tellus Lite V-Simulator 缓冲区错误漏洞 — Tellus Lite V-Simulator 7.8 High2023-01-16
CVE-2022-42281 NVIDIA DGX 缓冲区错误漏洞 — NVIDIA DGX servers 6.7 Medium2023-01-13
CVE-2023-21589 Adobe InDesign Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InDesign 7.8 High2023-01-13
CVE-2023-21590 Adobe InDesign Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InDesign 7.8 High2023-01-13
CVE-2023-21595 Adobe InCopy Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InCopy 7.8 High2023-01-13
CVE-2023-21597 Adobe InCopy Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability — InCopy 7.8 High2023-01-13
CVE-2023-22404 Junos OS: SRX Series and MX Series with SPC3: When IPsec VPN is configured iked will core when a specifically formatted payload is received — Junos OS 6.5 Medium2023-01-12
CVE-2023-22411 Junos OS: SRX Series: The flow processing daemon (flowd) will crash when Unified Policies are used with IPv6 and certain dynamic applications are rejected by the device — Junos OS 7.5 High2023-01-12
CVE-2023-22415 Junos OS: MX Series and SRX Series: The flow processing daemon (flowd) will crash when specific H.323 packets are received — Junos OS 7.5 High2023-01-12
CVE-2023-23456 Upx: heap-buffer-overflow in packtmt::pack() 5.3 Medium2023-01-12
CVE-2022-44431 Google Android OS和unisoc部分产品缓冲区错误漏洞 — SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8000 5.5 -2023-01-04

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