JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
jupyterlab · jupyterlab jupyterlite-core · jupyterlab notebook
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| jupyterlab PyPI |
|
|
| notebook PyPI |
|
|
jupyterlab · jupyterlab jupyterlite-core · jupyterlab notebook
| Product | Affected | Fixed in |
|---|---|---|
| jupyterlab PyPI |
|
|
| notebook PyPI |
|
|
| jupyterlite-core PyPI |
|
|
JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.7 until 4.5.11 and 4.6.4, the markdownviewer:trust and notebook:trust command-link handlers use tracker.currentWidget to resolve the current Markdown viewer or notebook when the user answers rather than retaining the document whose command button was clicked. If another document becomes current while the prompt is open and the user chooses Trust, JupyterLab marks the second document trusted while leaving the clicked document untrusted. Later command buttons in the incorrectly trusted document run without a prompt, and trusting a notebook marks all cells trusted, saves unsaved edits, and persists the server signature to disk. Applications that bundle JupyterLab, including affected Notebook and JupyterLite releases, inherit the behavior. This issue is fixed in versions 4.5.11 and 4.6.4.
From the CVE record · GitHub_M
JupyterLab’s Markdown viewer and notebook Trust command-link handlers can trust the wrong document if another document becomes current while the prompt is open and the user chooses Trust. Later command buttons in that incorrectly trusted document run without a prompt; trusting a notebook also marks all its cells trusted, saves unsaved edits, and persists the server signature to disk. Affected Notebook and JupyterLite releases inherit this behavior.
Check installations of PyPI jupyterlab 4.5.7–4.5.10 or 4.6.0–4.6.3, notebook 7.5.6–7.6.2, or jupyterlite-core 0.7.5–0.8.3.