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-22167 GPU DDK - Cache resident PM buffers writable by other GPU requestors, leading to arbitrary write to physical memory — Graphics DDK 7.8 -2026-05-01
CVE-2026-27890 Firebird has Pre-Auth DOS when Processing Out of Order CNCT_specific_data Segments — firebird 8.2 High2026-04-17
CVE-2026-34864 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.8 Medium2026-04-13
CVE-2026-4149 Sonos Era 300 SMB Response Out-Of-Bounds Access Remote Code Execution Vulnerability — Era 300 9.8 -2026-04-11
CVE-2026-34988 Wasmtime leaks data between pooling allocator instances — wasmtime 7.5AIHighAI2026-04-09
CVE-2026-39892 cryptography has a buffer overflow if non-contiguous buffers were passed to APIs — cryptography 8.1AIHighAI2026-04-08
CVE-2026-39863 Kamailio Core: TCP Data Processing Vulnerability — kamailio 7.5 High2026-04-08
CVE-2026-5475 NASA cFS CCSDS Header Size cfe_sb_priv.c CFE_SB_TransmitMsg memory corruption — cFS 5.5 Medium2026-04-03
CVE-2026-34159 llama.cpp: Unauthenticated RCE via GRAPH_COMPUTE buffer=0 bypass in llama.cpp RPC backend — llama.cpp 9.8 Critical2026-04-01
CVE-2026-33847 Improper Restriction of Operations within the Bounds of a Memory Buffer in linkingvision rapidvms — rapidvms 7.8 High2026-03-24
CVE-2026-33849 Improper Restriction of Operations within the Bounds of a Memory Buffer in linkingvision rapidvms — rapidvms 8.8 High2026-03-24
CVE-2026-33848 Improper Restriction of Operations within the Bounds of a Memory Buffer in linkingvision rapidvms — rapidvms 8.8 High2026-03-24
CVE-2026-33851 Improper Restriction of Operations within the Bounds of a Memory Buffer in joncampbell123 doslib — doslib 7.8 High2026-03-24
CVE-2026-4738 GDAL Bundled zlib (inftree9.c) Pointer Offset Optimization Undefined Behavior Allows Heap Corruption or Remote Code Execution — gdal 9.8 -2026-03-24
CVE-2026-4734 Heap Buffer Overflow in yoyofr/modizer — modizer 8.8 -2026-03-24
CVE-2026-4010 ThakeeNathees pocketlang pkByteBufferAddString memory corruption — pocketlang 3.3 Low2026-03-12
CVE-2026-30883 ImageMagick has a Heap Overflow when writing extremely large image profile in the PNG encoder — ImageMagick 5.7 Medium2026-03-09
CVE-2026-20024 Cisco Secure Firewall Adaptive Security Appliance和Cisco Secure Firewall Threat Defense 缓冲区错误漏洞 — Cisco Secure Firewall Adaptive Security Appliance (ASA) Software 6.8 Medium2026-03-04
CVE-2026-3437 Improper Restriction of Operations within the Bounds of a Memory Buffer in Portwell Engineering Toolkits — Portwell Engineering Toolkits 6.7AIMediumAI2026-03-03
CVE-2026-3394 jarikomppa soloud WAV File soloud_wav.cpp loadwav memory corruption — soloud 3.3 Low2026-03-01
CVE-2026-3382 ChaiScript boxed_number.hpp get_as memory corruption — ChaiScript 3.3 Low2026-03-01
CVE-2023-31364 AMD Processors 安全漏洞 — AMD EPYC™ 7001 Series Processors 6.5AIMediumAI2026-02-26
CVE-2026-3145 libvips matrixload.c vips_foreign_load_matrix_header memory corruption — libvips 5.3 Medium2026-02-25
CVE-2026-2522 Open5GS MME esm-build.c memory corruption — Open5GS 5.3 Medium2026-02-15
CVE-2026-2521 Open5GS SGW-C sgwc_s5c_handle_create_session_response memory corruption — Open5GS 5.3 Medium2026-02-15
CVE-2024-21961 AMD Processors 安全漏洞 — AMD EPYC™ 7002 Series Processors 6.5AIMediumAI2026-02-12
CVE-2026-2259 aardappel lobster Parsing parser.h ParseStatements memory corruption — lobster 3.3 Low2026-02-10
CVE-2026-2258 aardappel lobster wfc.h WaveFunctionCollapse memory corruption — lobster 3.3 Low2026-02-10
CVE-2026-2246 AprilRobotics apriltag apriltag.c apriltag_detector_detect memory corruption — apriltag 3.3 Low2026-02-09
CVE-2026-25634 iccDEV memcpy-param-overlap in CIccTagMultiProcessElement::Apply() — iccDEV 7.8 High2026-02-06

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