How severe is CVE-2019-17662?

No CVSS score has been assigned to CVE-2019-17662 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2019-17662?

Affected package information for CVE-2019-17662 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-17662?

No fixed release is recorded for CVE-2019-17662 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2019-17662 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2019-17662 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2019-17662 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2019-17662, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-17662?

CVE-2019-17662 has an EPSS (Exploit Prediction Scoring System) score of 96.8%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2019-17662?

CVE-2019-17662 is classified as Path Traversal (CWE-22), CWE-522 (CWE-522). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-17662?

A Nuclei detection template exists for CVE-2019-17662, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-17662 published, and has it been updated?

CVE-2019-17662 was published on October 16, 2019 and was last updated on August 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2019-17662 — Shashankmangal2

CVE-2019-17662 is a Path Traversal vulnerability. 6 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Oct 16, 2019

Updated

Aug 5, 2024

Affected

1 product

Patched

See advisory

Exploits

6 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

96.8%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

1 product · 1 configurations

Application

thinvnccybelsoft

1 version

1.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47519remotewindows✓ Verified

ThinVNC 1.0b1 - Authentication Bypass

by Nikhith Tumamlapalli · Oct 17, 2019

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2019-17662 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect CVE-2019-17662

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-17662 -u https://target

Template: ThinVNC 1.0b1 - Authentication Bypass
Severity: critical
Impact: An attacker can bypass authentication and gain unauthorized access to the ThinVNC application.
Remediation: Upgrade to a patched version of ThinVNC or implement additional authentication mechanisms.

Template by ProjectDiscovery nuclei-templates (DhiyaneshDK), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-17662 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works