Host process crash via oversized VNC clipboard message
Published Jan 23, 2020 · Updated Aug 6, 2024
Integer overflow in QEMU's VNC display driver before 2.1.0 allows remote authenticated users to crash the host process. The protocol_client_msg parser trusts the 32-bit ClientCutText length and adds eight without a bound, so wraparound keeps vnc_client_read in a loop that repeatedly allocates buffers. Reachability requires an enabled VNC display and endpoint access; exploitation hangs or terminates the affected QEMU instance and its guest.
Summary
What happened
Integer overflow in QEMU's VNC display driver before 2.1.0 allows remote authenticated users to crash the host process. The protocol_client_msg parser trusts the 32-bit ClientCutText length and adds eight without a bound, so wraparound keeps vnc_client_read in a loop that repeatedly allocates buffers. Reachability requires an enabled VNC display and endpoint access; exploitation hangs or terminates the affected QEMU instance and its guest.
The record
- CVE
- CVE-2015-5239
- Published
- Jan 23, 2020
- Updated
- Aug 6, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=before 2.1.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