Daemon crash via incorrect array-pointer dereference
Published May 24, 2021 · Updated Aug 3, 2024
Memory corruption in libvirt 6.10.0 through 7.0.0 release candidates allows remote authenticated users to crash libvirtd via node-device listing. Incorrect operator precedence in virNodeDeviceGetMdevTypesCaps dereferences the array pointer incorrectly while clearing mediated-device type entries. A read-only connection is sufficient, but the host must have a PCI device and driver that supports mediated devices; successful exploitation interrupts virtualization management.
Summary
What happened
Memory corruption in libvirt 6.10.0 through 7.0.0 release candidates allows remote authenticated users to crash libvirtd via node-device listing. Incorrect operator precedence in virNodeDeviceGetMdevTypesCaps dereferences the array pointer incorrectly while clearing mediated-device type entries. A read-only connection is sufficient, but the host must have a PCI device and driver that supports mediated devices; successful exploitation interrupts virtualization management.
The record
- CVE
- CVE-2021-3559
- Published
- May 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- libvirt
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 24, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 7.0.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.
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