The remote SUSE Linux SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:3744-1 advisory.

    Security fixes:

    - CVE-2024-8354: Fixed assertion failure in usb_ep_get() (bsc#1230834)
    - CVE-2024-8612: Fixed information leak in virtio devices (bsc#1230915)

    Update version to 8.2.7:

    Security fixes:

    - CVE-2024-7409: Fixed denial of service via improper synchronization in QEMU NBD Server during socket     closure (bsc#1229007)
    - CVE-2024-4693: Fixed improper release of configure vector in virtio-pci that lead to guest triggerable     crash (bsc#1224132)

    Other fixes:

    - added missing fix for ppc64 emulation that caused corruption in userspace (bsc#1230140)
    - target/ppc: Fix lxvx/stxvx facility check (bsc#1229929)
    - accel/kvm: check for KVM_CAP_READONLY_MEM on VM (bsc#1231519)

    Full changelog here:

    https://lore.kernel.org/qemu-devel/d9ff276f-f1ba-4e90-8343-a7a0dc2bf305@tls.msk.ru/

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of qemu installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-4693 advisory.

  - A flaw was found in the QEMU Virtio PCI Bindings (hw/virtio/virtio-pci.c). An improper release and use of     the irqfd for vector 0 during the boot process leads to a guest triggerable crash via vhost_net_stop().
    This flaw allows a malicious guest to crash the QEMU process on the host. (CVE-2024-4693)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - A flaw was found in the QEMU Virtio PCI Bindings (hw/virtio/virtio-pci.c). An improper release and use of     the irqfd for vector 0 during the boot process leads to a guest triggerable crash via vhost_net_stop().
    This flaw allows a malicious guest to crash the QEMU process on the host. (CVE-2024-4693)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:4094-1 advisory.

    Security fixes:

    - CVE-2024-8354: Fixed assertion failure in usb_ep_get() (bsc#1230834)
    - CVE-2024-8612: Fixed information leak in virtio devices (bsc#1230915)

    Update version to 8.2.7:

    Security fixes:

    - CVE-2024-7409: Fixed denial of service via improper synchronization in QEMU NBD Server during socket     closure (bsc#1229007)
    - CVE-2024-4693: Fixed improper release of configure vector in virtio-pci that lead to guest triggerable     crash (bsc#1224132)

    Other fixes:

    - added missing fix for ppc64 emulation that caused corruption in userspace (bsc#1230140)
    - target/ppc: Fix lxvx/stxvx facility check (bsc#1229929)
    - accel/kvm: check for KVM_CAP_READONLY_MEM on VM (bsc#1231519)

    Full changelog here:

    https://lore.kernel.org/qemu-devel/d9ff276f-f1ba-4e90-8343-a7a0dc2bf305@tls.msk.ru/

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of QEMU installed on the remote Windows host is prior to 9.0.0 and therefore vulnerable to the following:

  - A double free vulnerability was found in QEMU virtio devices (virtio-gpu, virtio-serial-bus, virtio-crypto), where     the mem_reentrancy_guard flag insufficiently protects against DMA reentrancy issues. This issue could allow a     malicious privileged guest user to crash the QEMU process on the host, resulting in a denial of service or allow     arbitrary code execution within the context of the QEMU process on the host. (CVE-2024-3446)

  - A stack based buffer overflow was found in the virtio-net device of QEMU. This issue occurs when flushing TX in     the virtio_net_flush_tx function if guest features VIRTIO_NET_F_HASH_REPORT, VIRTIO_F_VERSION_1 and     VIRTIO_NET_F_MRG_RXBUF are enabled. This could allow a malicious user to overwrite local variables allocated on the     stack. Specifically, the `out_sg` variable could be used to read a part of process memory and send it to the wire,     causing an information leak. (CVE-2023-6693)

  - A flaw was found in QEMU. An assertion failure was present in the update_sctp_checksum() function in     hw/net/net_tx_pkt.c when trying to calculate the checksum of a short-sized fragmented packet. This flaw allows a     malicious guest to crash QEMU and cause a denial of service condition. (CVE-2024-3567)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS / 24.10 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-7094-1 advisory.

    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)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
209545	SUSE SLES15: qemu / qemu-SLOF / qemu-accel-tcg-x86 / qemu-audio-alsa / etc (SUSE-SU-2024:3744-1)	Nessus	SuSE Local Security Checks	10/23/2024	6/26/2026	medium
296030	Azure Linux 3.0 Security Update: qemu (CVE-2024-4693)	Nessus	Azure Linux Local Security Checks	1/22/2026	1/22/2026	medium
228936	Linux Distros Unpatched Vulnerability : CVE-2024-4693	Nessus	Misc.	3/5/2025	7/27/2026	medium
212572	SUSE SLED15: qemu / qemu-SLOF / qemu-accel-qtest / qemu-accel-tcg-x86 / qemu-arm / etc (SUSE-SU-2024:4094-1)	Nessus	SuSE Local Security Checks	12/12/2024	6/26/2026	medium
200136	QEMU < 9.0.0 Multiple Vulnerabilities	Nessus	Windows	6/6/2024	7/12/2024	medium
210736	Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS / 24.10 : QEMU vulnerabilities (USN-7094-1)	Nessus	Ubuntu Local Security Checks	11/11/2024	1/21/2026	high

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

high