Authenticated guest agent disruption via unchecked timeout change
Published May 27, 2021 · Updated Aug 4, 2024
Missing authorization in Red Hat libvirt 5.10.0 through 6.1.0 allows remote authenticated users to interrupt QEMU guest agent commands. virDomainAgentSetResponseTimeout accepts read-only connections and applies an attacker-supplied timeout globally, including zero. A read-only libvirt connection is sufficient, and the resulting timeout causes guest agent operations to fail.
Summary
What happened
Missing authorization in Red Hat libvirt 5.10.0 through 6.1.0 allows remote authenticated users to interrupt QEMU guest agent commands. virDomainAgentSetResponseTimeout accepts read-only connections and applies an attacker-supplied timeout globally, including zero. A read-only libvirt connection is sufficient, and the resulting timeout causes guest agent operations to fail.
The record
- CVE
- CVE-2020-10701
- Published
- May 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- libvirt
- Classifications
- CWE-862, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libvirt 6.2.0
What conditions does exploitation require?
What is affected?
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