Wednesday, March 27, 2019

USN-3923-1: QEMU vulnerabilities

qemu vulnerabilities

A security issue affects these releases of Ubuntu and its derivatives:

  • Ubuntu 18.10
  • Ubuntu 18.04 LTS
  • Ubuntu 16.04 LTS
  • Ubuntu 14.04 LTS

Summary

Several security issues were fixed in QEMU.

Software Description

  • qemu - Machine emulator and virtualizer

Details

Michael Hanselmann discovered that QEMU incorrectly handled the Media Transfer Protocol (MTP). An attacker inside the guest could use this issue to read or write arbitrary files and cause a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 18.10. (CVE-2018-16867)

Michael Hanselmann discovered that QEMU incorrectly handled the Media Transfer Protocol (MTP). An attacker inside the guest could use this issue to read arbitrary files, contrary to expectations. This issue only affected Ubuntu 18.04 LTS and Ubuntu 18.10. (CVE-2018-16872)

Zhibin Hu discovered that QEMU incorrectly handled the Plan 9 File System support. An attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2018-19489)

Li Quang and Saar Amar discovered multiple issues in the QEMU PVRDMA device. An attacker inside the guest could use these issues to cause a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 18.10. These issues were resolved by disabling PVRDMA support in Ubuntu 18.10. (CVE-2018-20123, CVE-2018-20124, CVE-2018-20125, CVE-2018-20126, CVE-2018-20191, CVE-2018-20216)

Michael Hanselmann discovered that QEMU incorrectly handled certain i2c commands. A local attacker could possibly use this issue to read QEMU process memory. This issue only affected Ubuntu 18.04 LTS and Ubuntu 18.10. (CVE-2019-3812)

It was discovered that QEMU incorrectly handled the Slirp networking back-end. An attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service, or possibly execute arbitrary code on the host. In the default installation, when QEMU is used with libvirt, attackers would be isolated by the libvirt AppArmor profile. (CVE-2019-6778)

Update instructions

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

Ubuntu 18.10
qemu-system - 1:2.12+dfsg-3ubuntu8.6
qemu-system-arm - 1:2.12+dfsg-3ubuntu8.6
qemu-system-data - 1:2.12+dfsg-3ubuntu8.6
qemu-system-gui - 1:2.12+dfsg-3ubuntu8.6
qemu-system-mips - 1:2.12+dfsg-3ubuntu8.6
qemu-system-misc - 1:2.12+dfsg-3ubuntu8.6
qemu-system-ppc - 1:2.12+dfsg-3ubuntu8.6
qemu-system-s390x - 1:2.12+dfsg-3ubuntu8.6
qemu-system-sparc - 1:2.12+dfsg-3ubuntu8.6
qemu-system-x86 - 1:2.12+dfsg-3ubuntu8.6
Ubuntu 18.04 LTS
qemu-system - 1:2.11+dfsg-1ubuntu7.12
qemu-system-arm - 1:2.11+dfsg-1ubuntu7.12
qemu-system-mips - 1:2.11+dfsg-1ubuntu7.12
qemu-system-misc - 1:2.11+dfsg-1ubuntu7.12
qemu-system-ppc - 1:2.11+dfsg-1ubuntu7.12
qemu-system-s390x - 1:2.11+dfsg-1ubuntu7.12
qemu-system-sparc - 1:2.11+dfsg-1ubuntu7.12
qemu-system-x86 - 1:2.11+dfsg-1ubuntu7.12
Ubuntu 16.04 LTS
qemu-system - 1:2.5+dfsg-5ubuntu10.36
qemu-system-aarch64 - 1:2.5+dfsg-5ubuntu10.36
qemu-system-arm - 1:2.5+dfsg-5ubuntu10.36
qemu-system-mips - 1:2.5+dfsg-5ubuntu10.36
qemu-system-misc - 1:2.5+dfsg-5ubuntu10.36
qemu-system-ppc - 1:2.5+dfsg-5ubuntu10.36
qemu-system-s390x - 1:2.5+dfsg-5ubuntu10.36
qemu-system-sparc - 1:2.5+dfsg-5ubuntu10.36
qemu-system-x86 - 1:2.5+dfsg-5ubuntu10.36
Ubuntu 14.04 LTS
qemu-system - 2.0.0+dfsg-2ubuntu1.45
qemu-system-aarch64 - 2.0.0+dfsg-2ubuntu1.45
qemu-system-arm - 2.0.0+dfsg-2ubuntu1.45
qemu-system-mips - 2.0.0+dfsg-2ubuntu1.45
qemu-system-misc - 2.0.0+dfsg-2ubuntu1.45
qemu-system-ppc - 2.0.0+dfsg-2ubuntu1.45
qemu-system-sparc - 2.0.0+dfsg-2ubuntu1.45
qemu-system-x86 - 2.0.0+dfsg-2ubuntu1.45

To update your system, please follow these instructions: https://wiki.ubuntu.com/Security/Upgrades.

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

References



from Ubuntu Security Notices https://ift.tt/2UYEFZ9

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.