Adjacent desktop control via unintended TigerVNC listener
Published Apr 14, 2025 · Updated Apr 15, 2025
Improper resource exposure in Project Jupyter Jupyter Remote Desktop Proxy 3.0.0 allows adjacent attackers to control a Linux desktop over VNC. setup_websockify passed -rfbunixpath to TigerVNC without -rfbport -1, so TigerVNC also bound an RFB TCP listener. The issue requires version 3.0.0 with TigerVNC and network reachability to its listener; TurboVNC deployments are unaffected.
Summary
What happened
Improper resource exposure in Project Jupyter Jupyter Remote Desktop Proxy 3.0.0 allows adjacent attackers to control a Linux desktop over VNC. setup_websockify passed -rfbunixpath to TigerVNC without -rfbport -1, so TigerVNC also bound an RFB TCP listener. The issue requires version 3.0.0 with TigerVNC and network reachability to its listener; TurboVNC deployments are unaffected.
The record
- CVE
- CVE-2025-32428
- Published
- Apr 14, 2025
- Updated
- Apr 15, 2025
- Vendor
- Project Jupyter
- Product
- Jupyter Remote Desktop Proxy
- Classifications
- CWE-668, T1021.005
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2025CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.0.0, < 3.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo