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 vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.
{
"severity": "CRITICAL",
"github_reviewed": true,
"cwe_ids": [
"CWE-668"
],
"nvd_published_at": "2025-04-15T00:15:14Z",
"github_reviewed_at": "2025-04-12T03:42:31Z"
}