Host-memory disclosure via uninitialized capset response
Published Jun 2, 2021 · Updated Aug 3, 2024
Information disclosure in QEMU 6.0 and earlier allows guest OS users to read host memory through the vhost-user GPU device. The virgl_cmd_get_capset_info() handler returns a partially filled response structure without first clearing it, exposing residual host-process bytes to the guest. Exploitation requires a guest able to query a virgl-enabled vhost-user-gpu backend; the demonstrated consequence is host-memory disclosure.
Summary
What happened
Information disclosure in QEMU 6.0 and earlier allows guest OS users to read host memory through the vhost-user GPU device. The virgl_cmd_get_capset_info() handler returns a partially filled response structure without first clearing it, exposing residual host-process bytes to the guest. Exploitation requires a guest able to query a virgl-enabled vhost-user-gpu backend; the demonstrated consequence is host-memory disclosure.
The record
- CVE
- CVE-2021-3545
- Published
- Jun 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-908, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 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=All QEMU versions up to and including 6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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