USN-4372-1: QEMU vulnerabilities

Publication date

21 May 2020

Overview

Several security issues were fixed in QEMU.


Packages

  • qemu - Machine emulator and virtualizer

Details

It was discovered that QEMU incorrectly handled bochs-display devices. A
local attacker in a guest could use this to cause a denial of service or
possibly execute arbitrary code in the host. This issue only affected
Ubuntu 19.10. (CVE-2019-15034)

It was discovered that QEMU incorrectly handled memory during certain VNC
operations. A remote attacker could possibly use this issue to cause QEMU
to consume resources, resulting in a denial of service. This issue only
affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 19.10.
(CVE-2019-20382)

It was discovered that QEMU incorrectly generated QEMU Pointer
Authentication signatures on ARM. A local attacker could possibly use this
issue to bypass PAuth. This issue only affected Ubuntu 19.10.
(CVE-2020-10702)

Ziming Zhang discovered that QEMU incorrectly...

It was discovered that QEMU incorrectly handled bochs-display devices. A
local attacker in a guest could use this to cause a denial of service or
possibly execute arbitrary code in the host. This issue only affected
Ubuntu 19.10. (CVE-2019-15034)

It was discovered that QEMU incorrectly handled memory during certain VNC
operations. A remote attacker could possibly use this issue to cause QEMU
to consume resources, resulting in a denial of service. This issue only
affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 19.10.
(CVE-2019-20382)

It was discovered that QEMU incorrectly generated QEMU Pointer
Authentication signatures on ARM. A local attacker could possibly use this
issue to bypass PAuth. This issue only affected Ubuntu 19.10.
(CVE-2020-10702)

Ziming Zhang discovered that QEMU incorrectly handled ATI VGA emulation. A
local attacker in a guest could use this issue to cause QEMU to crash,
resulting in a denial of service. This issue only affected Ubuntu 20.04
LTS. (CVE-2020-11869)

Aviv Sasson discovered that QEMU incorrectly handled Slirp networking. A
remote attacker could use this issue to cause QEMU to crash, resulting in a
denial of service, or possibly execute arbitrary code. This issue only
affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 19.10.
(CVE-2020-1983)


Update instructions

After a standard system update you need to restart all QEMU virtual machines to make all the necessary changes.

Learn more about how to get the fixes.

The problem can be corrected by updating your system to the following package versions:

Ubuntu Release Package Version
20.04 focal qemu –  1:4.2-3ubuntu6.1
qemu-system –  1:4.2-3ubuntu6.1
qemu-system-arm –  1:4.2-3ubuntu6.1
qemu-system-mips –  1:4.2-3ubuntu6.1
qemu-system-ppc –  1:4.2-3ubuntu6.1
qemu-system-s390x –  1:4.2-3ubuntu6.1
qemu-system-sparc –  1:4.2-3ubuntu6.1
qemu-system-x86 –  1:4.2-3ubuntu6.1
19.10 eoan qemu –  1:4.0+dfsg-0ubuntu9.6
qemu-system –  1:4.0+dfsg-0ubuntu9.6
qemu-system-arm –  1:4.0+dfsg-0ubuntu9.6
qemu-system-mips –  1:4.0+dfsg-0ubuntu9.6
qemu-system-ppc –  1:4.0+dfsg-0ubuntu9.6
qemu-system-s390x –  1:4.0+dfsg-0ubuntu9.6
qemu-system-sparc –  1:4.0+dfsg-0ubuntu9.6
qemu-system-x86 –  1:4.0+dfsg-0ubuntu9.6
18.04 bionic qemu –  1:2.11+dfsg-1ubuntu7.26
qemu-system –  1:2.11+dfsg-1ubuntu7.26
qemu-system-arm –  1:2.11+dfsg-1ubuntu7.26
qemu-system-mips –  1:2.11+dfsg-1ubuntu7.26
qemu-system-ppc –  1:2.11+dfsg-1ubuntu7.26
qemu-system-s390x –  1:2.11+dfsg-1ubuntu7.26
qemu-system-sparc –  1:2.11+dfsg-1ubuntu7.26
qemu-system-x86 –  1:2.11+dfsg-1ubuntu7.26
16.04 xenial qemu –  1:2.5+dfsg-5ubuntu10.44
qemu-system –  1:2.5+dfsg-5ubuntu10.44
qemu-system-aarch64 –  1:2.5+dfsg-5ubuntu10.44
qemu-system-arm –  1:2.5+dfsg-5ubuntu10.44
qemu-system-mips –  1:2.5+dfsg-5ubuntu10.44
qemu-system-ppc –  1:2.5+dfsg-5ubuntu10.44
qemu-system-s390x –  1:2.5+dfsg-5ubuntu10.44
qemu-system-sparc –  1:2.5+dfsg-5ubuntu10.44
qemu-system-x86 –  1:2.5+dfsg-5ubuntu10.44

Reduce your security exposure

Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.


Have additional questions?

Talk to a member of the team ›