Vulnerability details

CVE-2025-32428

jupyterhub jupyter-remote-desktop-proxy

Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended

CVSS 4.0
9.0Critical

Official 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.

CVSS scores

ScoreVersionSourceVector
9.0Critical 4.0 CVEProject cvelistV5 (CNA) (GitHub_M) CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Affected products

VendorProductVersionsSource
jupyterhub jupyter-remote-desktop-proxy >= 3.0.0, < 3.0.1 CVEProject cvelistV5 (CNA)

References and advisories

2
Kolun on Telegram @kolunsec Exploited CVEs, key news and a daily digest Alerts for this product's next CVEsFollow the product to get new vulnerabilities on Telegram.

Details

Published
2025-04-15
Last updated
2025-04-15
State
Published
Assigner (CNA)
GitHub_M

Exploit prediction (EPSS)

0.93%
Probability of exploitation in 30 days
60.9%
Percentile (among all CVEs)

SSVC assessment (CISA)

Automatable
Yes
Exploitation
None
Technical impact
Total

Weaknesses (CWE)

  • CWE-668
    Exposure of Resource to Wrong Sphere