Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter-remote-desktop-proxy were still accessible via the network. This vulnerability does not affect users having TurboVNC as the vncserver executable. This issue is fixed in 3.0.1.
Metrics
Affected Vendors & Products
References
History
Tue, 15 Apr 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Mon, 14 Apr 2025 23:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter-remote-desktop-proxy were still accessible via the network. This vulnerability does not affect users having TurboVNC as the vncserver executable. This issue is fixed in 3.0.1. | |
Title | Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended | |
Weaknesses | CWE-668 | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-04-15T02:54:15.365Z
Reserved: 2025-04-08T10:54:58.367Z
Link: CVE-2025-32428

Updated: 2025-04-15T02:54:11.299Z

Status : Awaiting Analysis
Published: 2025-04-15T00:15:14.880
Modified: 2025-04-15T18:39:27.967
Link: CVE-2025-32428

No data.