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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

1131 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, Availability Execute 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, Confidentiality Read 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.
Confidentiality Read 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)
Requirements Use 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 Design Use 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 Compilation Use 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
Implementation Consider 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 Compilation Run 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 ID Title CVSS Severity Published
CVE-2026-123268 libyal libvmdk Extent Data File libvmdk_extent_table.c libvmdk_extent_table_get_extent_data_file_path memory corruption — libvmdk 3.5 Low 2026-11-05
CVE-2026-122146 101arrowz fflate index.mjs unzipSync memory corruption — fflate 7.3 High 2026-11-05
CVE-2026-121074 Chrome Android 157 之前 GPU 内存损坏漏洞 — Chrome - - 2026-11-03
CVE-2026-121229 Chrome 157 前 Android 版 ANGLE 远程代码执行漏洞 — Chrome - - 2026-11-03
CVE-2026-120232 Horizon DataSys Reboot Restore Standard Kernel Driver shield.sys sub_23908 memory corruption — Reboot Restore Standard 8.8 High 2026-11-01
CVE-2026-116259 libimobiledevice Device Info afc.c afc_get_device_info_key memory corruption — libimobiledevice 5.3 Medium 2026-10-26
CVE-2026-20197 Multiple Cisco Products Snort 3 Teredo Protocol Denial of Service Vulnerability — Cisco Open Source Snort3 5.8 Medium 2026-10-21
CVE-2026-113003 Chrome 156 之前版本 HID 内存破坏漏洞 — Chrome - - 2026-10-20
CVE-2026-110914 Google Chrome<155.0.8059.84 Workers内存损坏漏洞 — Chrome - - 2026-10-15
CVE-2026-110920 Chrome<155.0.8059.84 V8堆损坏远程代码执行漏洞 — Chrome - - 2026-10-15
CVE-2026-110917 Chrome <155.0.8059.84 SVG内存损坏漏洞 — Chrome - - 2026-10-15
CVE-2026-110918 Chrome<155.0.8059.84内存损坏漏洞 — Chrome - - 2026-10-15
CVE-2026-110913 Google Chrome多个版本DOM内存损坏远程代码执行漏洞 — Chrome - - 2026-10-15
CVE-2026-45450 Unitronics - CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer — Unitronics UniStream Pro/UniLogic 8.3 High 2026-10-15
CVE-2026-96265 IBM Power Systems Firmware Improper Memory Buffer Restriction — PowerVM Hypervisor 8.2 High 2026-10-12
CVE-2026-84058 Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-84875 Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection — Guardium Data Protection 7.5 High 2026-10-08
CVE-2026-82335 IBM Guardium Data Protection Buffer Overflow — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-82344 IBM Guardium Data Protection Buffer Overflow — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-84290 Security vulnerability affects the Windows S-TAP component as part of IBM Guardium Data Protection — Guardium Data Protection 5.1 Medium 2026-10-08
CVE-2026-106067 Gimp: gimp: heap buffer overflow in hot color filter on oversized image — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-106066 Gimp: gimp: heap buffer overflow in raw data export on oversized image dimensions — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-106065 Gimp: gimp: heap buffer overflow in pcx export on oversized image dimensions — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-76464 Cisco Meraki Hardening Release October 2026 - Buffer Management Vulnerabilities — Cisco Campus Gateway Software 9.6 Critical 2026-10-07
CVE-2026-106064 Gimp: gimp: heap buffer overflow in gif export on oversized image dimensions — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-106062 Gimp: gimp: heap buffer overflow in dds loader on crafted directdraw surface file — Red Hat Enterprise Linux 9 7.8 High 2026-10-06
CVE-2026-106063 Gimp: gimp: heap buffer overflow in dicom export on oversized image dimensions — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-06
CVE-2026-47602 NVIDIA驱动解引用漏洞致拒绝服务与信息泄露 — GeForce 7.1 High 2026-09-30
CVE-2026-47550 NVIDIA Windows驱动内核空指针解引用漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-100892 aligungr UERANSIM nr-gnb handler.cpp ULInformationTransfer memory corruption — UERANSIM 5.3 Medium 2026-09-28

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