CVE-2018-1064
First published: Thu Mar 01 2018(Updated: )
An incomplete fix for <a href="https://access.redhat.com/security/cve/CVE-2018-5748">CVE-2018-5748</a> that affects QEMU monitor leading to a resource exhaustion but now also triggered via QEMU guest agent. Upstream patch: <a href="https://libvirt.org/git/?p=libvirt.git;a=commit;h=fbf31e1a4cd19d6f6e33e0937a009775cd7d9513">https://libvirt.org/git/?p=libvirt.git;a=commit;h=fbf31e1a4cd19d6f6e33e0937a009775cd7d9513</a>
Credit: secalert@redhat.com secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Debian Debian Linux | =7.0 | |
| Debian Debian Linux | =8.0 | |
| Debian Debian Linux | =9.0 | |
| Redhat Libvirt | <=4.1.0 | |
| redhat/libvirt | <4.2.0 | 4.2.0 |
| debian/libvirt | 7.0.0-3+deb11u3 9.0.0-4+deb12u2 10.10.0-3 |
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
- https://access.redhat.com/errata/RHSA-2018:1396
- https://access.redhat.com/errata/RHSA-2018:1929
- https://bugzilla.redhat.com/show_bug.cgi?id=1550672
- https://libvirt.org/git/?p=libvirt.git;a=commit;h=fbf31e1a4cd19d6f6e33e0937a009775cd7d9513
- https://lists.debian.org/debian-lts-announce/2018/03/msg00018.html
- https://usn.ubuntu.com/3680-1/
- https://www.debian.org/security/2018/dsa-4137
- https://launchpad.net/bugs/cve/CVE-2018-1064
- https://libvirt.org/git/?p=libvirt.git%3Ba=commit%3Bh=fbf31e1a4cd19d6f6e33e0937a009775cd7d9513
- https://access.redhat.com/security/cve/CVE-2018-5748
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1559517
- https://security.libvirt.org/2018/0004.html
- https://security-tracker.debian.org/tracker/CVE-2018-1064
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1064
- https://nvd.nist.gov/vuln/detail/CVE-2018-1064
- https://ubuntu.com/security/CVE-2018-1064
Frequently Asked Questions
What is CVE-2018-1064?
CVE-2018-1064 is a vulnerability in libvirt version before 4.2.0-rc1 that can result in resource exhaustion due to an incomplete fix for CVE-2018-5748.
What is the severity of CVE-2018-1064?
CVE-2018-1064 has a low severity rating.
How does CVE-2018-1064 affect libvirt?
CVE-2018-1064 affects libvirt versions before 4.2.0-rc1 and can be triggered via the QEMU guest agent.
What is the recommended version of libvirt to avoid CVE-2018-1064?
To avoid CVE-2018-1064, it is recommended to use libvirt version 4.2.0-rc1 or later.
Where can I find more information about CVE-2018-1064?
You can find more information about CVE-2018-1064 at the following references: [1] [2] [3].
- collector/nvd-index
- agent/type
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/remedy
- agent/author
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/severity
- agent/weakness
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2018-1064
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/tags
- agent/event
- agent/description
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- agent/trending
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/7.0
- version/debian debian linux/8.0
- version/debian debian linux/9.0
- vendor/redhat
- canonical/redhat libvirt
- version/redhat libvirt/4.1.0
- package-manager/redhat
- package-manager/debian