Denial of service via leaked IOThread stats array
Published Apr 28, 2020 · Updated Aug 4, 2024
libvirt 4.10.0 through 6.x before 6.1.0 allows remote authenticated users with read-only connections to cause denial of service via domstats. The qemuDomainGetStatsIOThread function returns a NULL-terminated IOThread statistics array when no IOThreads exist, but neither it nor its caller frees the allocation, leaking memory on repeated virDomainListGetStats requests. Exploitation requires a libvirt read-only connection and can exhaust daemon memory, interrupting service without providing confidentiality or integrity impact.
Summary
What happened
libvirt 4.10.0 through 6.x before 6.1.0 allows remote authenticated users with read-only connections to cause denial of service via domstats. The qemuDomainGetStatsIOThread function returns a NULL-terminated IOThread statistics array when no IOThreads exist, but neither it nor its caller frees the allocation, leaking memory on repeated virDomainListGetStats requests. Exploitation requires a libvirt read-only connection and can exhaust daemon memory, interrupting service without providing confidentiality or integrity impact.
The record
- CVE
- CVE-2020-12430
- Published
- Apr 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2020CVE 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?
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.
Weakness, pattern, technique
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