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-2024-13941 ouch-org ouch zip.rs convert_zip_date_time memory corruption — ouch 5.3 Medium2025-04-01
CVE-2025-3001 PyTorch torch.lstm_cell memory corruption — PyTorch 5.3 Medium2025-03-31
CVE-2025-3000 PyTorch torch.jit.script memory corruption — PyTorch 5.3 Medium2025-03-31
CVE-2025-2999 PyTorch torch.nn.utils.rnn.unpack_sequence memory corruption — PyTorch 5.3 Medium2025-03-31
CVE-2025-2998 PyTorch torch.nn.utils.rnn.pad_packed_sequence memory corruption — PyTorch 5.3 Medium2025-03-31
CVE-2018-25109 Nintendo Animal Crossing Letter Trigram ac-exploit-gc memory corruption — Animal Crossing 6.4 Medium2025-03-23
CVE-2025-2401 Buffer overflow in Immunity Debugger — Immunity Debugger 7.8 -2025-03-17
CVE-2025-2357 DCMTK dcmjpls JPEG-LS Decoder memory corruption — DCMTK 6.3 Medium2025-03-17
CVE-2025-25175 Siemens Simcenter Femap 缓冲区错误漏洞 — Simcenter Femap V2401 7.8 High2025-03-13
CVE-2025-23400 Siemens Teamcenter Visualization和Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Teamcenter Visualization V14.3 7.8 High2025-03-11
CVE-2025-23398 Siemens Teamcenter 缓冲区错误漏洞 — Teamcenter Visualization V14.3 7.8 High2025-03-11
CVE-2025-23397 Siemens Teamcenter Visualization和Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Teamcenter Visualization V14.3 7.8 High2025-03-11
CVE-2025-2148 PyTorch Tuple torch.ops.profiler._call_end_callbacks_on_jit_fut memory corruption — PyTorch 5.0 Medium2025-03-10
CVE-2025-2029 MicroDicom DICOM Viewer mDicom.exe memory corruption — DICOM Viewer 5.3 Medium2025-03-06
CVE-2025-1866 Undefined Behavior Due to Out-of-Bounds Pointer Arithmetic in libwebsockets — libwebsockets 9.8 -2025-03-03
CVE-2025-1864 Buffer Overflow and Potential Code Execution in Radare2 — radare2 7.8 -2025-03-03
CVE-2025-26597 Xorg: xwayland: buffer overflow in xkbchangetypesofkey() 7.8 High2025-02-25
CVE-2025-1378 radare2 rasm2 rasm2.c memory corruption — radare2 3.3 Low2025-02-17
CVE-2025-1352 GNU elfutils eu-readelf libdw_alloc.c __libdw_thread_tail memory corruption — elfutils 5.0 Medium2025-02-16
CVE-2025-1215 vim main.c memory corruption — vim 2.8 Low2025-02-12
CVE-2023-31352 AMD Server Processor 缓冲区错误漏洞 — AMD EPYC™ 9004 Processors 6.0 Medium2025-02-11
CVE-2025-1182 GNU Binutils ld elflink.c bfd_elf_reloc_symbol_deleted_p memory corruption — Binutils 5.0 Medium2025-02-11
CVE-2025-1181 GNU Binutils ld elflink.c _bfd_elf_gc_mark_rsec memory corruption — Binutils 5.0 Medium2025-02-11
CVE-2025-1180 GNU Binutils ld elf-eh-frame.c _bfd_elf_write_section_eh_frame memory corruption — Binutils 3.1 Low2025-02-11
CVE-2025-1179 GNU Binutils ld libbfd.c bfd_putl64 memory corruption — Binutils 5.0 Medium2025-02-11
CVE-2025-1178 GNU Binutils ld libbfd.c bfd_putl64 memory corruption — Binutils 5.6 Medium2025-02-11
CVE-2025-1153 GNU Binutils format.c bfd_set_format memory corruption — Binutils 3.1 Low2025-02-10
CVE-2024-11611 AutomationDirect C-More EA9 EAP9 File Parsing Memory Corruption Remote Code Execution Vulnerability — C-More EA9 7.8 -2025-01-30
CVE-2024-11610 AutomationDirect C-More EA9 EAP9 File Parsing Memory Corruption Remote Code Execution Vulnerability — C-More EA9 7.8 -2025-01-30
CVE-2025-0574 Sante PACS Server URL path Memory Corruption Denial-of-Service Vulnerability — PACS Server 7.5 -2025-01-30

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