CVE-2017-5931: Integer Overflow
Integer overflow in hw/virtio/virtio-crypto.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (QEMU process crash) or possibly execute arbitrary code on the host via a crafted virtio-crypto request, which triggers a heap-based buffer overflow.
Other sources
Quick Emulator(Qemu) built with the Virtio crypto device emulation support is vulnerable to an integer overflow issue. It could occur while handling data encryption/decryption requests in 'virtiocryptohandlesymreq'.
A privileged user inside guest could use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on the host with privileges of the Qemu process.
Upstream patch: --------------- -> https://lists.nongnu.org/archive/html/qemu-devel/2017-01/msg01368.html
Reference: ---------- -> http://www.openwall.com/lists/oss-security/2017/02/07/8
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-5931?
CVE-2017-5931 has a severity rating of High due to its potential to cause a denial of service and possible arbitrary code execution.
How do I fix CVE-2017-5931?
To mitigate CVE-2017-5931, upgrade to QEMU version 2.8.1.2 or later, which addresses the integer overflow vulnerability.
Who is affected by CVE-2017-5931?
Local guest OS privileged users of QEMU versions prior to 2.8.1.2 are affected by CVE-2017-5931.
What are the potential impacts of CVE-2017-5931?
The impacts of CVE-2017-5931 include the possibility of a QEMU process crash and the risk of executing arbitrary code on the host.
What component of QEMU does CVE-2017-5931 affect?
CVE-2017-5931 specifically affects the hw/virtio/virtio-crypto.c component of QEMU.