What is the severity of CVE-2017-5578?

CVE-2017-5578 is classified as a denial of service vulnerability that can lead to significant memory consumption on the host.

How do I fix CVE-2017-5578?

To mitigate CVE-2017-5578, you should upgrade to the latest version of QEMU beyond 2.8.1.1 where the vulnerability has been patched.

What systems are affected by CVE-2017-5578?

CVE-2017-5578 affects QEMU versions up to and including 2.8.1.1.

What is the main impact of exploiting CVE-2017-5578?

Exploiting CVE-2017-5578 can lead to a denial of service by exhausting host memory through excessive VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.

Who can exploit CVE-2017-5578?

CVE-2017-5578 can be exploited by local users of a guest operating system running on an affected QEMU instance.

Vulnerability/
CVE-2017-5578

medium

6.5

CWE

401

15/3/2017

12/2/2023

CVE-2017-5578

First published: Wed Mar 15 2017(Updated: )

Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
QEMU KVM	<=2.8.1.1

Remedy

http://www.openwall.com/lists/oss-security/2017/01/23/3

Remedy

http://www.openwall.com/lists/oss-security/2017/01/25/2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5578?
CVE-2017-5578 is classified as a denial of service vulnerability that can lead to significant memory consumption on the host.
How do I fix CVE-2017-5578?
To mitigate CVE-2017-5578, you should upgrade to the latest version of QEMU beyond 2.8.1.1 where the vulnerability has been patched.
What systems are affected by CVE-2017-5578?
CVE-2017-5578 affects QEMU versions up to and including 2.8.1.1.
What is the main impact of exploiting CVE-2017-5578?
Exploiting CVE-2017-5578 can lead to a denial of service by exhausting host memory through excessive VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.
Who can exploit CVE-2017-5578?
CVE-2017-5578 can be exploited by local users of a guest operating system running on an affected QEMU instance.

agent/weakness
agent/references
agent/severity
agent/author
agent/type
agent/description
agent/event
agent/first-publish-date
agent/remedy
agent/tags
agent/last-modified-date
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
vendor/qemu
canonical/qemu kvm
version/qemu kvm/2.8.1.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-5578?
CVE-2017-5578 is classified as a denial of service vulnerability that can lead to significant memory consumption on the host.
How do I fix CVE-2017-5578?
To mitigate CVE-2017-5578, you should upgrade to the latest version of QEMU beyond 2.8.1.1 where the vulnerability has been patched.
What systems are affected by CVE-2017-5578?
CVE-2017-5578 affects QEMU versions up to and including 2.8.1.1.
What is the main impact of exploiting CVE-2017-5578?
Exploiting CVE-2017-5578 can lead to a denial of service by exhausting host memory through excessive VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.
Who can exploit CVE-2017-5578?
CVE-2017-5578 can be exploited by local users of a guest operating system running on an affected QEMU instance.