Advisory

USN-7094-1

Also known as: CVE-2019-20382, CVE-2020-13765, CVE-2020-1983, CVE-2020-7039, CVE-2020-8608, CVE-2021-3592, CVE-2021-3594, CVE-2023-3019, CVE-2024-4693, CVE-2024-7730

Summary

qemu vulnerabilities

Details

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 14.04 LTS. (CVE-2019-20382)

It was discovered that QEMU incorrectly handled certain memory copy
operations when loading ROM contents. If a user were tricked into running
an untrusted kernel image, a remote attacker could possibly use this issue
to run arbitrary code. This issue only affected Ubuntu 14.04 LTS.
(CVE-2020-13765)

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 14.04 LTS. (CVE-2020-1983)

It was discovered that the SLiRP networking implementation of the QEMU
emulator did not properly manage memory under certain circumstances. An
attacker could use this to cause a heap-based buffer overflow or other out-
of-bounds access, which can lead to a denial of service (application crash)
or potential execute arbitrary code. This issue only affected
Ubuntu 14.04 LTS. (CVE-2020-7039)

It was discovered that the SLiRP networking implementation of the QEMU
emulator misuses snprintf return values. An attacker could use this to
cause a denial of service (application crash) or potentially execute
arbitrary code. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-8608)

It was discovered that QEMU SLiRP networking incorrectly handled certain
udp packets. An attacker inside a guest could possibly use this issue to
leak sensitive information from the host. This issue only affected
Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2021-3592, CVE-2021-3594)

It was discovered that QEMU had a DMA reentrancy issue, leading to a
use-after-free vulnerability. An attacker could possibly use this issue
to cause a denial of service. This issue only affected Ubuntu 18.04 LTS,
Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2023-3019)

It was discovered that QEMU had a flaw in Virtio PCI Bindings, leading
to a triggerable crash via vhost_net_stop. An attacker inside a guest
could possibly use this issue to cause a denial of service. This issue
only affected Ubuntu 24.04 LTS and Ubuntu 24.10. (CVE-2024-4693)

It was discovered that QEMU incorrectly handled memory in virtio-sound,
leading to a heap-based buffer overflow. An attacker could possibly use
this issue to cause a denial of service or execute arbitrary code. This
issue only affected Ubuntu 24.04 LTS and Ubuntu 24.10. (CVE-2024-7730)

Severity

Not rated by the source.

Dates

Published
2024-11-08 01:42 UTC
Modified
2026-06-29 13:51 UTC

Affected packages and fixes

qemu

Debian packages (deb) · Ubuntu 20.04

Affected

  • introduced 0, fixed 1:4.2-3ubuntu6.30 (ecosystem)

Fixed versions

1:4.2-3ubuntu6.30

Fix

  • Fixed version 1:4.2-3ubuntu6.30
    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 22.04

Affected

  • introduced 0, fixed 1:6.2+dfsg-2ubuntu6.24 (ecosystem)

Fixed versions

1:6.2+dfsg-2ubuntu6.24

Fix

  • Fixed version 1:6.2+dfsg-2ubuntu6.24
    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 24.04

Affected

  • introduced 0, fixed 1:8.2.2+ds-0ubuntu1.4 (ecosystem)

Fixed versions

1:8.2.2+ds-0ubuntu1.4

Fix

  • Fixed version 1:8.2.2+ds-0ubuntu1.4
    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