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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-119 (内存缓冲区边界内操作的限制不恰当) — Vulnerability Class 1064

1064 vulnerabilities classified as CWE-119 (内存缓冲区边界内操作的限制不恰当). AI Chinese analysis included.

CWE-119 represents a critical memory safety weakness where software performs read or write operations beyond the intended boundaries of a memory buffer. This flaw typically arises from insufficient validation of input lengths or loop counters, allowing attackers to manipulate program execution flow. By crafting malicious inputs that exceed buffer limits, adversaries can overwrite adjacent memory, corrupt data structures, or inject executable code, often leading to remote code execution or system crashes. Developers mitigate this risk by implementing rigorous bounds checking before any memory access, utilizing safe string handling functions that enforce length limits, and adopting modern programming languages with automatic memory management. Additionally, employing static analysis tools and fuzzing techniques during development helps identify out-of-bounds accesses early, ensuring that all buffer operations remain strictly within allocated memory regions to prevent exploitation.

MITRE CWE Description
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Common Consequences (3)
Integrity, Confidentiality, AvailabilityExecute Unauthorized Code or Commands, Modify Memory
If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can alter the intended control flow by redirecting a funct…
Availability, ConfidentialityRead Memory, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)
Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
ConfidentialityRead Memory
In the case of an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffer's position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.
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)
This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.
void host_lookup(char *user_supplied_addr){ struct hostent *hp; in_addr_t *addr; char hostname[64]; in_addr_t inet_addr(const char *cp); /*routine that ensures user_supplied_addr is in the right format for conversion */ validate_addr_form(user_supplied_addr); addr = inet_addr(user_supplied_addr); hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET); strcpy(hostname, hp->h_name); }
Bad · C
This example applies an encoding procedure to an input string and stores it into a buffer.
char * copy_input(char *user_supplied_string){ int i, dst_index; char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE); if ( MAX_SIZE <= strlen(user_supplied_string) ){ die("user string too long, die evil hacker!"); } dst_index = 0; for ( i = 0; i < strlen(user_supplied_string); i++ ){ if( '&' == user_supplied_string[i] ){ dst_buf[dst_index++] = '&'; dst_buf[dst_index++] = 'a'; dst_buf[dst_index++] = 'm'; dst_buf[dst_index++] = 'p'; dst_buf[dst_index++] = ';'; } else if ('<' == user_supplied_string[i] ){ /* encode to &lt; */ } else dst_buf[dst_index++] = user_supplied_string[i]; } return ds
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2026-1998 micropython runtime.c mp_import_all memory corruption — micropython 3.3 Low2026-02-06
CVE-2026-25585 iccDEV vulnerable to OOB in CIccXform3DLut::Apply() — iccDEV 7.8 High2026-02-04
CVE-2026-25584 iccDEV vulnerable to Stack-based Buffer Overflow in CIccTagFloatNum::GetValues() — iccDEV 7.8 High2026-02-04
CVE-2026-25583 iccDEV vulnerable to Heap Buffer Overflow in CIccFileIO::Read8() — iccDEV 7.8 High2026-02-04
CVE-2026-24798 An Uninitialized stack variable vulnerability in GaijinEntertainment/DagorEngine — DagorEngine 8.4AIHighAI2026-01-27
CVE-2026-24794 Chunk Unloading Security Vulnerability in CardboardPowered/cardboard — cardboard 9.8AICriticalAI2026-01-27
CVE-2026-1465 A heap-based buffer over-read or buffer overflow in tildearrow/furnace — anyRTC-RTMP-OpenSource 9.8AICriticalAI2026-01-27
CVE-2026-1260 Invalid Memory Access in Sentencepiece, — Sentencepiece 6.2 -2026-01-22
CVE-2025-58409 GPU DDK - Disguised freelist buffers passed to RGXCreateHWRTDataSet can cause arbitrary physical memory writes corrupting memory — Graphics DDK 7.8AIHighAI2026-01-13
CVE-2025-15413 wasm3 m3_exec.h op_CallIndirect memory corruption — wasm3 5.3 Medium2026-01-01
CVE-2025-15411 WebAssembly wabt wasm-decompile InsertNode memory corruption — wabt 5.3 Medium2026-01-01
CVE-2025-12771 IBM Concert Software Improper Restriction of Operations within the Bounds of a Memory Buffer. — Concert 7.8 High2025-12-26
CVE-2025-14407 Soda PDF Desktop PDF File Parsing Memory Corruption Information Disclosure Vulnerability — Desktop 5.5AIMediumAI2025-12-23
CVE-2025-14419 pdfforge PDF Architect PDF File Parsing Memory Corruption Remote Code Execution Vulnerability — PDF Architect 7.8AIHighAI2025-12-23
CVE-2024-9684 FreyrSCADA Embedded Solution IEC 60870-5-104 Protocol 缓冲区错误漏洞 — IEC-60870-5-104 7.5 High2025-12-23
CVE-2025-68615 Net-SNMP snmptrapd crash — net-snmp 9.8 Critical2025-12-22
CVE-2025-53619 Grassroot DICOM 缓冲区错误漏洞 — Grassroot DICOM 7.4 High2025-12-16
CVE-2025-53618 Grassroot DICOM 缓冲区错误漏洞 — Grassroot DICOM 7.4 High2025-12-16
CVE-2025-52582 Grassroot DICOM 安全漏洞 — Grassroot DICOM 7.4 High2025-12-16
CVE-2025-48429 Grassroot DICOM 安全漏洞 — Grassroot DICOM 7.4 High2025-12-16
CVE-2025-14607 OFFIS DCMTK dcmdata dcbytstr.cc makeDicomByteString memory corruption — DCMTK 6.3 Medium2025-12-13
CVE-2025-14572 UTT 进取 512W formWebAuthGlobalConfig memory corruption — 进取 512W 8.8 High2025-12-12
CVE-2020-36881 Flexsense DiskBoss 'Add Input Directory' Buffer Overflow — DiskBoss 8.4 -2025-12-05
CVE-2020-36880 Flexsense DiskBoss 'Reports and Data Directory' Buffer Overflow — DiskBoss 7.8 -2025-12-05
CVE-2025-64713 WebAssembly Micro Runtime frame_offset_bottom array bounds overflow in fast Interpreter mode when handling GET_GLOBAL(I32) followed by if opcode — wasm-micro-runtime 5.1 Medium2025-11-25
CVE-2025-33195 NVIDIA DGX Spark 缓冲区错误漏洞 — DGX Spark 4.4 Medium2025-11-25
CVE-2025-13547 D-Link DIR-822K/DWR-M920 formDdns memory corruption — DIR-822K 8.8 High2025-11-23
CVE-2025-9338 ASUS Armoury Crate 安全漏洞 — Armoury Crate 7.8 -2025-11-06
CVE-2025-62594 ImageMagick CLAHE : Unsigned underflow and division-by-zero lead to OOB pointer arithmetic and process crash (DoS) — ImageMagick 4.7 Medium2025-10-27
CVE-2025-55089 Eclipse ThreadX FileX RAM disk driver buffer overflow — FileX 9.1AICriticalAI2025-10-16

Vulnerabilities classified as CWE-119 (内存缓冲区边界内操作的限制不恰当) represent 1064 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.