Potential authentication and CSRF tokens leak in JupyterLab
jupyterlab
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| jupyterlab PyPI |
|
|
| notebook PyPI |
|
|
jupyterlab
| Product | Affected | Fixed in |
|---|---|---|
| jupyterlab PyPI |
|
|
| notebook PyPI |
|
|
JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture. Users of JupyterLab who click on a malicious link may get their `Authorization` and `XSRFToken` tokens exposed to a third party when running an older `jupyter-server` version. JupyterLab versions 4.1.0b2, 4.0.11, and 3.6.7 are patched. No workaround has been identified, however users should ensure to upgrade `jupyter-server` to version 2.7.2 or newer which includes a redirect vulnerability fix.
From the CVE record · GitHub_M
Affected JupyterLab users running an older jupyter-server version may expose their Authorization and XSRFToken tokens to a third party if they click a malicious link. User interaction is required; the input does not specify whether attacker authentication is needed.
Check installations of PyPI jupyterlab versions below 3.6.7 or from 4.0.0 through 4.0.10, and PyPI notebook versions from 7.0.0 through 7.0.6.