Advisory

USN-3923-1

Also known as: CVE-2018-16867, CVE-2018-16872, CVE-2018-19489, CVE-2018-20123, CVE-2018-20124, CVE-2018-20125, CVE-2018-20126, CVE-2018-20191, CVE-2018-20216, CVE-2019-3812, CVE-2019-6778

Summary

qemu vulnerabilities

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)

Severity

Not rated by the source.

Dates

Published
2019-03-27 12:10 UTC
Modified
2026-02-10 04:41 UTC

Affected packages and fixes

qemu

Debian packages (deb) · Ubuntu 14.04

Affected

  • introduced 0, fixed 2.0.0+dfsg-2ubuntu1.45 (ecosystem)

Fixed versions

2.0.0+dfsg-2ubuntu1.45

Fix

  • Fixed version 2.0.0+dfsg-2ubuntu1.45
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

qemu

Debian packages (deb) · Ubuntu 16.04

Affected

  • introduced 0, fixed 1:2.5+dfsg-5ubuntu10.36 (ecosystem)

Fixed versions

1:2.5+dfsg-5ubuntu10.36

Fix

  • Fixed version 1:2.5+dfsg-5ubuntu10.36
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

qemu

Debian packages (deb) · Ubuntu 18.04

Affected

  • introduced 0, fixed 1:2.11+dfsg-1ubuntu7.12 (ecosystem)

Fixed versions

1:2.11+dfsg-1ubuntu7.12

Fix

  • Fixed version 1:2.11+dfsg-1ubuntu7.12
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Ubuntu Security Notices · CC BY-SA 4.0

Sources & licences