CVE-2024-42458: neatvnc · Improper Input Validation
Affects neatvncSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.8.1 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.8.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade any1/neatvnc to 0.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubany1/neatvncpkg:github/any1/neatvncOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-42458, organizations should take the following specific actions: 1) Monitor official Neat VNC channels for the release of version 0.8.1 or later that addresses this vulnerability and apply patches immediately upon availability. 2) Until patches are available, restrict network access to Neat VNC servers by implementing firewall rules that limit connections to trusted IP addresses and internal networks only. 3) Employ network segmentation to isolate VNC servers from critical assets and reduce the attack surface. 4) Disable or remove Neat VNC services on systems where remote desktop access is not essential. 5) Use VPNs or other secure tunneling mechanisms to protect remote access sessions and prevent direct exposure of VNC ports to the internet. 6) Enable logging and continuous monitoring of VNC server activity to detect anomalous connection attempts or unusual traffic patterns indicative of exploitation attempts. 7) Conduct vulnerability scanning and penetration testing focused on VNC services to identify and remediate exposure proactively. 8) Educate IT staff about this vulnerability and ensure incident response plans include procedures for VNC-related compromises. These targeted measures go beyond generic advice by focusing on network-level controls, access restrictions, and proactive detection tailored to the nature of this vulnerability.
Description
server.c in Neat VNC (aka neatvnc) before 0.8.1 does not properly validate the security type, a related issue to CVE-2006-2369.
References
- github.com/any1/neatvnc/commit/cc71650a69abc2573a0d96d082409d2468802d47 (opens in a new tab)
- github.com/any1/neatvnc/compare/v0.8.0...v0.8.1 (opens in a new tab)
- github.com/any1/neatvnc/releases/tag/v0.8.1 (opens in a new tab)
- openwall.com/lists/oss-security/2024/08/02/1 (opens in a new tab)
- openwall.com/lists/oss-security/2024/08/02/7 (opens in a new tab)
- openwall.com/lists/oss-security/2024/08/02/10 (opens in a new tab)