Jupyter Remote Desktop Proxy
Approved changes feed: RSS · Atom
cpe:2.3:a:jupyterhub:jupyter-remote-desktop-proxy:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Jupyterhub (b9fc67de-411f-5996-aa79-a32cff5a7e29) |
|---|---|
| Product | Jupyter Remote Desktop Proxy (20aa74c6-747c-5166-91f5-2d267c0a2b85) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-32428 |
vulnerable | 2026-06-08 07:18:59.744471 |
Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended
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.
Published: 2025-04-14T23:29:40.494Z
Updated: 2025-04-15T02:54:15.365Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.