JupyterLab jupyterlab-desktop
JupyterLab Desktop: One-Click Jupyter Server Token Leak leading to Remote Code Execution
JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop exposed getServerInfo to the renderer without confirming that the current page still had the local Jupyter server origin. In a local managed session using JupyterLab before 4.4.8, an attacker can place a crafted MathJax link in an untrusted notebook. If a victim opens the notebook and clicks the link, the existing renderer navigates to an attacker-controlled site while retaining access to the preload bridge. The site can call getServerInfo to obtain the local server URL and authentication token, then use the Jupyter REST API to create and trust a notebook that executes arbitrary code as the victim. Users whose environment already uses JupyterLab 4.4.8 or later are unaffected because the corrected link handling breaks the first step of the chain. This vulnerability is fixed in 4.6.2-1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 4.6.2-1
Fixed in 4.6.2-1
Mitigation
Upgrade jupyterlab-desktop to 4.6.2-1 or later.
References
- Vendor advisory github.com/jupyterlab/jupyterlab-desktop/secur…
- Patch github.com/jupyterlab/jupyterlab-desktop/commi…
- Release notes github.com/jupyterlab/jupyterlab-desktop/relea…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.