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-2024-20098 MediaTek 芯片 安全漏洞 — MT6768, MT6779, MT6781, MT6785, MT6833, MT6853, MT6873, MT6877, MT6885, MT6893, MT8188, MT8532, MT8675, MT8766, MT8768, MT8781, MT8786, MT8788 6.7 -2024-10-07
CVE-2024-20103 MediaTek 芯片 安全漏洞 — MT3605, MT6985, MT6989, MT6990, MT7927, MT8183, MT8512, MT8678, MT8695, MT8698, MT8796, MT8893 9.8 -2024-10-07
CVE-2024-20101 MediaTek 芯片 安全漏洞 — MT3605, MT6985, MT6989, MT6990, MT7927, MT8183, MT8512, MT8676, MT8678, MT8695, MT8698, MT8755, MT8775, MT8792, MT8796 9.8 -2024-10-07
CVE-2024-20100 MediaTek 芯片 安全漏洞 — MT3605, MT6985, MT6989, MT6990, MT7927, MT8183, MT8365, MT8512, MT8676, MT8678, MT8695, MT8698, MT8755, MT8775, MT8792, MT8796 9.8 -2024-10-07
CVE-2024-20092 MediaTek 芯片 安全漏洞 — MT6761, MT6765, MT6768, MT6779, MT6785, MT6853, MT6873, MT6885, MT8385, MT8666, MT8667, MT8766, MT8768, MT8781, MT8788, MT8789 6.7 -2024-10-07
CVE-2024-20090 MediaTek 芯片 安全漏洞 — MT6761, MT6765, MT6768, MT6779, MT6785, MT6853, MT6873, MT6885, MT8385, MT8666, MT8667, MT8766, MT8768, MT8781, MT8788, MT8789 6.7 -2024-10-07
CVE-2024-9482 Out of Bounds write on scan of malformed Mach-O file may crash the application — Antivirus 5.1 Medium2024-10-04
CVE-2024-9481 Out of Bounds write on scan of malformed eml file may crash the application — Antivirus 5.1 Medium2024-10-04
CVE-2024-6442 Bluetooth: ASCS Unchecked tailroom of the response buffer — Zephyr 6.3 Medium2024-10-04
CVE-2024-47134 JTEKT Kostac PLC Programming Software 安全漏洞 — Kostac PLC Programming Software (Former name: Koyo PLC Programming Software) 7.8 High2024-10-03
CVE-2024-20501 Cisco AnyConnect VPN 安全漏洞 — Cisco Meraki MX Firmware 8.6 High2024-10-02
CVE-2024-20499 Cisco Meraki Z Series Teleworker Gateway和Cisco Meraki MX 安全漏洞 — Cisco Meraki MX Firmware 8.6 High2024-10-02
CVE-2024-7672 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-09-30
CVE-2024-7671 DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software — Navisworks Freedom 7.8 High2024-09-30
CVE-2022-49039 Synology Drive 安全漏洞 — Synology Drive Client 6.7 Medium2024-09-26
CVE-2024-20496 Cisco SD-WAN vEdge Routers Denial of Service Vulnerability — Cisco SD-WAN vEdge Cloud 6.1 Medium2024-09-25
CVE-2024-43496 Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability — Microsoft Edge (Chromium-based) 6.5 Medium2024-09-19
CVE-2024-45769 Pcp: pmcd heap corruption through metric pmstore operations 5.5 Medium2024-09-19
CVE-2024-6259 BT: HCI: adv_ext_report Improper discarding in adv_ext_report — Zephyr 7.6 High2024-09-13
CVE-2024-43760 Photoshop Desktop | Out-of-bounds Write (CWE-787) — Photoshop Desktop 7.8 High2024-09-13
CVE-2024-45109 Photoshop Desktop | Out-of-bounds Write (CWE-787) — Photoshop Desktop 7.8 High2024-09-13
CVE-2024-45108 Photoshop Desktop | Out-of-bounds Write (CWE-787) — Photoshop Desktop 7.8 High2024-09-13
CVE-2024-39384 Premiere Pro | Out-of-bounds Write (CWE-787) — Premiere Pro 7.8 High2024-09-13
CVE-2024-39381 After Effects | Out-of-bounds Write (CWE-787) — After Effects 7.8 High2024-09-13
CVE-2024-41859 After Effects | Out-of-bounds Write (CWE-787) — After Effects 7.8 High2024-09-13
CVE-2024-39377 Media Encoder | Out-of-bounds Write (CWE-787) — Media Encoder 7.8 High2024-09-13
CVE-2024-39378 Audition | Out-of-bounds Write (CWE-787) — Audition 7.8 High2024-09-11
CVE-2024-7970 Google Chrome 安全漏洞 — Chrome 8.8AIHighAI2024-09-03
CVE-2024-39816 Arkcompiler Ets Runtime has an out-of-bounds write vulnerability — OpenHarmony 8.4 High2024-09-02
CVE-2024-38386 Arkcompiler Ets Runtime has an out-of-bounds write vulnerability — OpenHarmony 8.4 High2024-09-02

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