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-2025-2521 Lack of indexes’ validation against buffer borders leads to remote code execution. — C300 PCNT02 8.6 High2025-07-10
CVE-2025-34096 Easy File Sharing HTTP Server 7.2 Buffer Overflow via POST to /sendemail.ghp — Easy File Sharing HTTP Server 9.8AICriticalAI2025-07-10
CVE-2025-6693 RT-Thread device.c sys_device_write memory corruption — RT-Thread 7.8 High2025-06-26
CVE-2025-6543 Memory overflow vulnerability leading to unintended control flow and Denial of Service — ADC 9.8AICriticalAI2025-06-25
CVE-2025-52566 llama.cpp tokenizer signed vs. unsigned heap overflow — llama.cpp 8.6 High2025-06-24
CVE-2025-49847 llama.cpp Vulnerable to Buffer Overflow via Malicious GGUF Model — llama.cpp 8.8 High2025-06-17
CVE-2025-47869 Apache NuttX RTOS: examples/xmlrpc: Fix calls buffers size. — Apache NuttX RTOS 9.8AICriticalAI2025-06-16
CVE-2025-5869 RT-Thread lwp_syscall.c sys_recvfrom memory corruption — RT-Thread 8.0 High2025-06-09
CVE-2025-5865 RT-Thread Parameter lwp_syscall.c sys_select memory corruption — RT-Thread 8.0 High2025-06-09
CVE-2025-5648 Radare2 radiff2 pal.c r_cons_pal_init memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-5647 Radare2 radiff2 cons.c r_cons_context_break_pop memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-5646 Radare2 radiff2 pal.c r_cons_rainbow_free memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-5645 Radare2 radiff2 pal.c r_cons_pal_init memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-5643 Radare2 radiff2 cons.c cons_stack_load memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-5642 Radare2 radiff2 pal.c r_cons_pal_init memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-5641 Radare2 radiff2 cons.c r_cons_is_breaked memory corruption — Radare2 2.5 Low2025-06-05
CVE-2025-1246 Mali GPU Userspace Driver allows an Out-of-Bounds access — Bifrost GPU Userspace Driver 8.8AIHighAI2025-06-02
CVE-2025-5245 GNU Binutils objdump debug.c debug_type_samep memory corruption — Binutils 5.3 Medium2025-05-27
CVE-2025-5244 GNU Binutils ld elflink.c elf_gc_sweep memory corruption — Binutils 5.3 Medium2025-05-27
CVE-2025-35003 Apache NuttX RTOS: NuttX Bluetooth Stack HCI and UART DoS/RCE Vulnerabilities. — Apache NuttX RTOS 8.8AIHighAI2025-05-26
CVE-2025-5099 KL-001-2025-004: Mobile Dynamix PrinterShare Mobile Print Out-of-bounds Write — PrinterShare Mobile Print 8.8AIHighAI2025-05-23
CVE-2025-46333 z2d OOB composition could lead to invalid memory access and corruption — z2d 5.3 -2025-04-25
CVE-2025-24797 Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow — firmware 9.4 Critical2025-04-14
CVE-2025-32033 Apollo Router Operation Limits Vulnerable to Bypass via Integer Overflow — router 7.5 High2025-04-07
CVE-2025-0050 Mali GPU Userspace Driver allows an Out-of-Bounds access — Valhall GPU Userspace Driver 5.4AIMediumAI2025-04-07
CVE-2025-3145 MindSpore mindspore.numpy.fft.rfft2 memory corruption — MindSpore 3.3 Low2025-04-03
CVE-2025-3144 MindSpore mindspore.numpy.fft.hfftn memory corruption — MindSpore 3.3 Low2025-04-03
CVE-2025-3136 PyTorch CUDACachingAllocator.cpp torch.cuda.memory.caching_allocator_delete memory corruption — PyTorch 3.3 Low2025-04-03
CVE-2025-3121 PyTorch torch.jit.jit_module_from_flatbuffer memory corruption — PyTorch 3.3 Low2025-04-02
CVE-2024-45064 STMicroelectronics X-CUBE-AZRTOS-WL 缓冲区错误漏洞 — X-CUBE-AZRT-H7RS 8.5 High2025-04-02

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