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-11683 YAML::Syck versions before 1.36 for Perl has missing Null-Terminators which causes Out-of-Bounds Read and potential Information Disclosure — YAML::Syck 7.5AIHighAI2025-10-16
CVE-2025-60016 BIG-IP SSL/TLS vulnerability — BIG-IP 7.5 High2025-10-15
CVE-2025-33044 exFat Memory Corruption Issue — AptioV 7.1AIHighAI2025-10-14
CVE-2025-11423 Tenda CH22 SafeEmailFilter formSafeEmailFilter memory corruption — CH22 9.8 Critical2025-10-08
CVE-2025-36156 IBM InfoSphere Data Replication VSAM for z/OS Remote Source code execution — InfoSphere Data Replication VSAM for z/OS Remote Source 7.4 High2025-10-07
CVE-2025-10995 Open Babel zipstreamimpl.h underflow memory corruption — Open Babel 5.3 Medium2025-09-26
CVE-2025-21483 Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity — Snapdragon 9.8 Critical2025-09-24
CVE-2025-26503 Buffer manipulation — VxWorks 7 6.7 Medium2025-09-18
CVE-2025-8001 Ashlar-Vellum Cobalt CO File Parsing Memory Corruption Remote Code Execution Vulnerability — Cobalt 7.8AIHighAI2025-09-17
CVE-2025-10225 Incorrect Memory Allocation in OpenSSL-Based Session Module in AxxonSoft Axxon One (C-Werk) — AxxonOne C-Werk 7.5 High2025-09-10
CVE-2025-58750 rAthena missing bound check in chclif_parse_moveCharSlot — rathena 8.2 High2025-09-09
CVE-2023-31351 AMD Embedded Processors和AMD Server Processor 安全漏洞 — AMD EPYC™ 7003 Series Processors 5.3 Medium2025-09-06
CVE-2025-9732 DCMTK dcm2img diybrpxt.h memory corruption — DCMTK 5.3 Medium2025-08-31
CVE-2025-7776 Memory overflow vulnerability leading to unpredictable or erroneous behavior and Denial of Service — ADC 7.5AIHighAI2025-08-26
CVE-2025-7775 Memory overflow vulnerability leading to Remote Code Execution and/or Denial of Service — ADC 9.8 -2025-08-26
CVE-2025-9389 vim memmove-vec-unaligned-erms.S __memmove_avx_unaligned_erms memory corruption — vim 3.3 Low2025-08-24
CVE-2025-55286 z2d OOB drawing with new multi-sample anti-aliasing could lead to invalid memory access and corruption — z2d 8.8AIHighAI2025-08-16
CVE-2025-8961 LibTIFF tiffcrop tiffcrop.c main memory corruption — LibTIFF 3.3 Low2025-08-14
CVE-2025-55159 slab allows out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check — slab 8.1AIHighAI2025-08-11
CVE-2025-8746 GNU libopts __strstr_sse2 memory corruption — libopts 3.3 Low2025-08-09
CVE-2025-4423 SetupAutomationSmm:Vulnerability in the SMM module allow attacker to write arbitrary code and lead to memory corruption — InsydeH2O 8.2 High2025-07-30
CVE-2025-53715 TP-Link TL-WR841N Wan6to4TunnelCfgRpm.htm buffer overflow — TL-WR841N V11 7.5AIHighAI2025-07-29
CVE-2025-53714 TP-Link TL-WR841N WzdWlanSiteSurveyRpm_AP.htm buffer overflow — TL-WR841N V11 7.5AIHighAI2025-07-29
CVE-2025-33077 IBM Engineering Systems Design Rhapsody code execution — Engineering Systems Design Rhapsody 8.8 High2025-07-23
CVE-2025-33076 IBM Engineering Systems Design Rhapsody code execution — Engineering Systems Design Rhapsody 8.8 High2025-07-23
CVE-2025-7299 IrfanView CADImage Plugin DWG File Parsing Memory Corruption Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7325 IrfanView CADImage Plugin DXF File Parsing Memory Corruption Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7323 IrfanView CADImage Plugin DWG File Parsing Memory Corruption Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7321 IrfanView CADImage Plugin DWG File Parsing Memory Corruption Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7320 IrfanView CADImage Plugin DXF File Parsing Memory Corruption Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21

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