Viewer crash via ZRLE heap buffer overflows
Published Jan 2, 2020 · Updated Aug 6, 2024
Heap buffer overflows in TigerVNC before 1.3.1 allow remote VNC servers to crash vncviewer through crafted ZRLE screen data. The ZRLE_DECODE routine in common/rfb/zrleDecode.h writes decoded screen-image data beyond heap buffers when NDEBUG removes its assertion checks. A user must connect the viewer to an attacker-controlled server; the confirmed outcome is a viewer crash, while arbitrary code execution remains unconfirmed.
Summary
What happened
Heap buffer overflows in TigerVNC before 1.3.1 allow remote VNC servers to crash vncviewer through crafted ZRLE screen data. The ZRLE_DECODE routine in common/rfb/zrleDecode.h writes decoded screen-image data beyond heap buffers when NDEBUG removes its assertion checks. A user must connect the viewer to an attacker-controlled server; the confirmed outcome is a viewer crash, while arbitrary code execution remains unconfirmed.
The record
- CVE
- CVE-2014-0011
- Published
- Jan 2, 2020
- Updated
- Aug 6, 2024
- Vendor
- TigerVNC
- Product
- TigerVNC
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 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 1.3.1
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.
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