Guest-triggered process crash via mismatched crypto lengths
Published Aug 3, 2023 · Updated Sep 25, 2024
Heap buffer overflow in QEMU's virtio-crypto device allows guest OS users to crash the QEMU process via a malformed request. The helper trusts unequal src_len and dst_len values when sizing symmetric encryption or decryption buffers instead of rejecting the request. Exploitation requires high privileges in a guest with the virtio-crypto device exposed and can terminate the associated virtual machine process without disclosing or modifying data.
Summary
What happened
Heap buffer overflow in QEMU's virtio-crypto device allows guest OS users to crash the QEMU process via a malformed request. The helper trusts unequal src_len and dst_len values when sizing symmetric encryption or decryption buffers instead of rejecting the request. Exploitation requires high privileges in a guest with the virtio-crypto device exposed and can terminate the associated virtual machine process without disclosing or modifying data.
The record
- CVE
- CVE-2023-3180
- Published
- Aug 3, 2023
- Updated
- Sep 25, 2024
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-122, CWE-787, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 3, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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