Client crash via anonymous TLS credential dereference
Published Jun 17, 2020 · Updated Aug 4, 2024
NULL pointer dereference in LibVNCClient of LibVNCServer before 0.9.13 allows remote attackers to crash clients through anonymous TLS. open_ssl_connection reads cred->x509Credential.x509CrlVerifyMode before checking anonymous TLS mode, where cred is NULL. Reachability requires the OpenSSL-backed client to negotiate anonymous TLS with a VNC server; the demonstrated consequence is a client-process crash.
Summary
What happened
NULL pointer dereference in LibVNCClient of LibVNCServer before 0.9.13 allows remote attackers to crash clients through anonymous TLS. open_ssl_connection reads cred->x509Credential.x509CrlVerifyMode before checking anonymous TLS mode, where cred is NULL. Reachability requires the OpenSSL-backed client to negotiate anonymous TLS with a VNC server; the demonstrated consequence is a client-process crash.
The record
- CVE
- CVE-2020-14396
- Published
- Jun 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Upstream anonymous TLS crash demonstrationproof of concept · demonstrated
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