Skip to content
Fencer Intel
critical 9.8

CVE-2019-17662 in the critical feed json

ThinVNC 1.0b1 is vulnerable to arbitrary file read, which leads to a compromise of the VNC server.

published 7y ago modified 4mo ago also EUVD-2019-7967

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
96.8%
EPSS 96.8% chance of exploitation in 30 days, percentile 99.8%
public exploits
2
Metasploit and Exploit-DB, plus a Nuclei check

Summary

ThinVNC 1.0b1 is vulnerable to arbitrary file read, which leads to a compromise of the VNC server. The vulnerability exists even when authentication is turned on during the deployment of the VNC server. The password for authentication is stored in cleartext in a file that can be read via a ../../ThinVnc.ini directory traversal attack vector.

Is CVE-2019-17662 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit auxiliary/scanner/http/thinvnc_traversal)
  2. Published

Exploit prediction

96.76% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.