Guest API blockage via retained monitor job
Published Mar 19, 2020 · Updated Aug 5, 2024
Denial of service in libvirt before 6.0.0 allows guest OS users to block libvirtd operations for a guest through its agent. The QEMU driver retains the guest's monitor job while waiting for an agent query, so a nonresponsive malicious agent prevents competing monitor work from proceeding. A guest administrator must control or stall the configured guest agent; the bounded consequence is API blockage for operations involving that guest.
Summary
What happened
Denial of service in libvirt before 6.0.0 allows guest OS users to block libvirtd operations for a guest through its agent. The QEMU driver retains the guest's monitor job while waiting for an agent query, so a nonresponsive malicious agent prevents competing monitor work from proceeding. A guest administrator must control or stall the configured guest agent; the bounded consequence is API blockage for operations involving that guest.
The record
- CVE
- CVE-2019-20485
- Published
- Mar 19, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo