jupyterlab
Affected
- introduced
4.0.0, fixed4.0.11(ecosystem)
Fixed versions
4.0.11
Fix
- Fixed version
4.0.11pip install --upgrade jupyterlab==4.0.11
Advisory
Also known as: BIT-jupyter-base-notebook-2024-22421, BIT-jupyter-notebook-2024-22421, BIT-jupyterlab-2024-22421, CVE-2024-22421, PYSEC-2026-1706, PYSEC-2026-2534
JupyterLab vulnerable to potential authentication and CSRF tokens leak
Impact
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.
Patches
JupyterLab 4.1.0b2, 4.0.11, and 3.6.7 were patched.
Workarounds
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.
References
Vulnerability reported by user @davwwwx via the bug bounty program sponsored by the European Commission and hosted on the Intigriti platform.
High Basis: The source's own band: HIGH
4.0.0, fixed 4.0.11 (ecosystem)4.0.11
4.0.11pip install --upgrade jupyterlab==4.0.110, fixed 3.6.7 (ecosystem)3.6.7
3.6.7pip install --upgrade jupyterlab==3.6.77.0.0, fixed 7.0.7 (ecosystem)7.0.7
7.0.7pip install --upgrade notebook==7.0.7Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0