{"uuid": "c69cd835-158c-447f-8ac4-b8e44378cf93", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-32428", "type": "seen", "source": "https://t.me/cvedetector/22900", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-32428 - Jupyter Remote Desktop Proxy Network Accessible VNC Server Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-32428 \nPublished : April 15, 2025, 12:15 a.m. | 34\u00a0minutes ago \nDescription : 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-15T03:13:14.000000Z"}