CVE-2024-42049 json
TightVNC (Server for Windows) before 2.8.84 allows attackers to connect to the control pipe via a network connection.
published 2y ago modified 4mo ago also EUVD-2024-39417
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
TightVNC (Server for Windows) before 2.8.84 allows attackers to connect to the control pipe via a network connection.
Patch / fix
- tightvnc tightvnc 2.8.84
Is CVE-2024-42049 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 FencerTimeline
- Published
- First public exploit (EDB-52322)
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
2.39% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- EDB-52322 TightVNC 2.8.83 - Control Pipe Manipulation local, 2025-06-09
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- tightvnc tightvnc
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
Sources
- CVE List CVE-2024-42049
- NVD CVE-2024-42049
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.