CVE-2023-27830

CVE-2023-27830 is a critical-severity vulnerability in Tightvnc with a CVSS 3.x base score of 9.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-269.

Key facts

Description

TightVNC before v2.8.75 allows attackers to escalate privileges on the host operating system via replacing legitimate files with crafted files when executing a file transfer. This is due to the fact that TightVNC runs in the backend as a high-privileges account.

Frequently asked questions

What is CVE-2023-27830?
TightVNC before v2.8.75 allows attackers to escalate privileges on the host operating system via replacing legitimate files with crafted files when executing a file transfer. This is due to the fact that TightVNC runs in the backend as a high-privileges account.
How severe is CVE-2023-27830?
CVE-2023-27830 has a CVSS 3.x base score of 9.0, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-27830 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-27830?
CVE-2023-27830 affects Tightvnc. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-27830?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2023-27830 published?
CVE-2023-27830 was published on 2023-04-12 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Tightvnc

All CVEs affecting Tightvnc →

Other CWE-269 (Improper Privilege Management) vulnerabilities

Browse all CWE-269 (Improper Privilege Management) vulnerabilities →