CVE-2013-4377: Use After Free
First published: Thu Sep 26 2013(Updated: )
A dangling pointer access flaw was found in the way qemu handled hot-unplugging virtio devices. This flaw was introduced by virtio refactoring and exists in the virtio-pci implementation. When the virtio-blk-pci device is deleted, the virtio-blk-device is removed first (removal is done in post-order). Later, the virtio-blk-device is accessed again, but proxy->vdev->vq is no longer valid (a dangling pointer) and kvm_set_ioeventfd_pio fails. A privileged guest user could use this flaw to crash the qemu process on the host system, causing a denial of service to it and any other running virtual machines. Patches are available at <a href="http://thread.gmane.org/gmane.comp.emulators.qemu/234440">http://thread.gmane.org/gmane.comp.emulators.qemu/234440</a> Acknowledgements: This issue was discovered by Sibiao Luo of Red Hat.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| QEMU KVM | =1.4.0 | |
| QEMU KVM | =1.4.1 | |
| QEMU KVM | =1.4.2 | |
| QEMU KVM | =1.5.0 | |
| QEMU KVM | =1.5.0-rc1 | |
| QEMU KVM | =1.5.0-rc2 | |
| QEMU KVM | =1.5.0-rc3 | |
| QEMU KVM | =1.5.1 | |
| QEMU KVM | =1.5.2 | |
| QEMU KVM | =1.5.3 | |
| QEMU KVM | =1.6.0 | |
| QEMU KVM | =1.6.0-rc1 | |
| QEMU KVM | =1.6.0-rc2 | |
| QEMU KVM | =1.6.0-rc3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://thread.gmane.org/gmane.comp.emulators.qemu/234440
- http://www.openwall.com/lists/oss-security/2013/09/26/4
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1012641
- http://www.openwall.com/lists/oss-security/2013/09/26/5
- https://bugzilla.redhat.com/show_bug.cgi?id=1012633
- http://lists.nongnu.org/archive/html/qemu-devel/2013-09/msg03347.html
- http://secunia.com/advisories/55015
- http://www.ubuntu.com/usn/USN-2092-1
Frequently Asked Questions
What is the severity of CVE-2013-4377?
CVE-2013-4377 is considered a high severity vulnerability due to the risk of arbitrary code execution caused by a dangling pointer access.
How do I fix CVE-2013-4377?
To fix CVE-2013-4377, upgrade QEMU to version 1.6.0 or later, as it includes the necessary patches.
Which versions of QEMU are affected by CVE-2013-4377?
CVE-2013-4377 affects QEMU versions 1.4.0 through 1.6.0-rc3.
What type of vulnerability is CVE-2013-4377?
CVE-2013-4377 is a dangling pointer access flaw specific to the virtio-pci implementation.
Can CVE-2013-4377 lead to data loss?
Yes, CVE-2013-4377 can potentially lead to data loss by allowing attackers to execute arbitrary code when hot-unplugging virtio devices.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/references
- agent/remedy
- agent/author
- agent/event
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2013-4377
- agent/trending
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- agent/source
- vendor/qemu
- canonical/qemu kvm
- version/qemu kvm/1.4.0
- version/qemu kvm/1.4.1
- version/qemu kvm/1.4.2
- version/qemu kvm/1.5.0
- version/qemu kvm/1.5.0-rc1
- version/qemu kvm/1.5.0-rc2
- version/qemu kvm/1.5.0-rc3
- version/qemu kvm/1.5.1
- version/qemu kvm/1.5.2
- version/qemu kvm/1.5.3
- version/qemu kvm/1.6.0
- version/qemu kvm/1.6.0-rc1
- version/qemu kvm/1.6.0-rc2
- version/qemu kvm/1.6.0-rc3