What is the git hash of the commit that fixed the venom vulnerability for qemu? – 2017

what is the git hash of the commit that fixed the venom vulnerability for qemu?
venom-graphic





VENOM, CVE-2015-3456, is a security vulnerability in the virtual floppy drive code used by many computer virtualization platforms. This vulnerability may allow an attacker to escape from the confines of an affected virtual machine (VM) guest and potentially obtain code-execution access to the host.




projects / qemu.git / commitdiff

During processing of certain commands such as FD_CMD_READ_ID and
FD_CMD_DRIVE_SPECIFICATION_COMMAND the fifo memory access could
get out of bounds leading to memory corruption with values coming
from the guest.

Fix this by making sure that the index is always bounded by the
allocated memory.

http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e907746266721f305d67bc0718795fedee2e824c




If you administer a system running Xen, KVM, or the native QEMU client, review and apply the latest patches developed to address this vulnerability.

If you have a vendor service or device using one of the affected hypervisors, contact the vendor’s support team to see if their staff has applied the latest VENOM patches.

Is it possible to patch KVM/Xen hypervisors without needing a reboot?
Our friends at Endurance International Group have provided instructions for a procedure to apply VENOM patches for KVM and XEN hypervisors without reboots using libvirt’s virsh commands. You can find their procedure documented at venomfix.com
Visit: http://venom.crowdstrike.com/

Related posts:

Leave a Reply