Host memory exhaustion via VNC disconnect leak
Published Mar 5, 2020 · Updated Aug 5, 2024
Memory leak in QEMU 4.1.0 allows remote authenticated users to exhaust host memory by disconnecting from a VNC server. zrle_compress_data initializes libz state on a local VncState, but vnc_zrle_clear passes the connection VncState to deflateEnd, which returns Z_STREAM_ERROR without freeing the allocation. Reachability requires VNC access with ZRLE or Tight encoding enabled; repeated disconnects consume host memory until resource exhaustion interrupts service.
Summary
What happened
Memory leak in QEMU 4.1.0 allows remote authenticated users to exhaust host memory by disconnecting from a VNC server. zrle_compress_data initializes libz state on a local VncState, but vnc_zrle_clear passes the connection VncState to deflateEnd, which returns Z_STREAM_ERROR without freeing the allocation. Reachability requires VNC access with ZRLE or Tight encoding enabled; repeated disconnects consume host memory until resource exhaustion interrupts service.
The record
- CVE
- CVE-2019-20382
- Published
- Mar 5, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.003
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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