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-2026-24800 A heap-based buffer over-read or buffer overflow in tildearrow/furnace — furnace 9.8AICriticalAI2026-01-27
CVE-2026-24799 A heap-based buffer over-read or buffer overflow in davisking/dlib — dlib 9.8AICriticalAI2026-01-27
CVE-2026-24797 An out of bounds write due to a missing bounds check in neka-nat/cupoch — cupoch 7.8AIHighAI2026-01-27
CVE-2026-24795 An Out-of-bounds Write in CloverHackyColor/CloverBootloader — CloverBootloader 7.8AIHighAI2026-01-27
CVE-2026-24793 A heap-based buffer over-read or buffer overflow vulnerability in azerothcore/azerothcore-wotlk — azerothcore-wotlk 8.4AIHighAI2026-01-27
CVE-2026-1284 Out-Of-Bounds Write vulnerability affecting the EPRT file reading procedure in SOLIDWORKS eDrawings from Release SOLIDWORKS Desktop 2025 through Release SOLIDWORKS Desktop 2026 — SOLIDWORKS eDrawings 7.8 High2026-01-26
CVE-2025-27821 HDFS native client: Out of bounds write in URI parser of native HDFS client — HDFS native client 9.8AICriticalAI2026-01-26
CVE-2026-1418 GPAC SRT Subtitle Import text_to_bifs.c gf_text_import_srt_bifs out-of-bounds write — GPAC 5.3 Medium2026-01-26
CVE-2025-14237 Canon多款产品 安全漏洞 — Satera LBP670C Series 9.8 Critical2026-01-15
CVE-2025-14236 Canon多款产品 安全漏洞 — Satera LBP670C Series 9.8 Critical2026-01-15
CVE-2025-14235 Canon多款产品 安全漏洞 — Satera LBP670C Series 9.8 Critical2026-01-15
CVE-2025-14234 Canon多款产品 安全漏洞 — Satera LBP670C Series 9.8 Critical2026-01-15
CVE-2025-14232 Canon多款产品 安全漏洞 — Satera LBP670C Series 9.8 Critical2026-01-15
CVE-2025-14231 Canon多款产品 安全漏洞 — Satera LBP670C Series 9.8 Critical2026-01-15
CVE-2021-47786 Redragon Gaming Mouse - 'REDRAGON_MOUSE.sys' Denial of Service (PoC) — Redragon Gaming Mouse 7.5 High2026-01-15
CVE-2021-47785 Ether_MP3_CD_Burner 1.3.8 - Buffer Overflow (SEH) — Ether_MP3_CD_Burner 9.8 Critical2026-01-15
CVE-2021-47781 Cmder Console Emulator 1.3.18 - 'Cmder.exe' Denial of Service (PoC) — Cmder Console Emulator 9.8 Critical2026-01-15
CVE-2021-47774 Kingdia CD Extractor 3.0.2 - Buffer Overflow (SEH) — Kingdia CD Extractor 9.8 Critical2026-01-15
CVE-2021-47775 YouTube Video Grabber 1.9.9.1 - Buffer Overflow (SEH) — YouTube Video Grabber 8.4 High2026-01-15
CVE-2021-47772 10-Strike Network Inventory Explorer Pro 9.31 - Buffer Overflow (SEH) — Strike Network Inventory Explorer Pro 9.8 Critical2026-01-15
CVE-2021-47765 AbsoluteTelnet 11.24 - 'Username' Denial of Service (PoC) — AbsoluteTelnet 5.5 Medium2026-01-15
CVE-2021-47764 AbsoluteTelnet 11.24 - 'Phone' Denial of Service (PoC) — AbsoluteTelnet 5.5 Medium2026-01-15
CVE-2026-0961 Out-of-bounds Write in Wireshark — Wireshark 5.5 Medium2026-01-14
CVE-2026-0962 Out-of-bounds Write in Wireshark — Wireshark 5.3 Medium2026-01-14
CVE-2026-0959 Out-of-bounds Write in Wireshark — Wireshark 5.3 Medium2026-01-14
CVE-2026-22853 FreeRDP has a heap-buffer-overflow in ndr_read_uint8Array — FreeRDP 9.8 -2026-01-14
CVE-2026-22852 FreeRDP has a heap-buffer-overflow in audin_process_formats — FreeRDP 9.1 -2026-01-14
CVE-2026-22211 TinyOS <= 2.1.2 Global Buffer Overflow in printfUART — TinyOS 9.8AICriticalAI2026-01-14
CVE-2025-12053 egwindrvx64.sys is potentially vulnerable to a buffer overflow — InsydeH2O tools 7.8 High2026-01-14
CVE-2025-12052 egwindrv.sys is potentially vulnerable to a buffer overflow. — InsydeH2O tools 7.8 High2026-01-14

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