Advisory

GHSA-44cc-43rp-5947

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

Summary

JupyterLab vulnerable to potential authentication and CSRF tokens leak

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-01-19 20:28 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

jupyterlab

PyPI · All systems

Affected

  • introduced 4.0.0, fixed 4.0.11 (ecosystem)

Fixed versions

4.0.11

Fix

  • Fixed version 4.0.11
    pip install --upgrade jupyterlab==4.0.11

jupyterlab

PyPI · All systems

Affected

  • introduced 0, fixed 3.6.7 (ecosystem)

Fixed versions

3.6.7

Fix

  • Fixed version 3.6.7
    pip install --upgrade jupyterlab==3.6.7

notebook

PyPI · All systems

Affected

  • introduced 7.0.0, fixed 7.0.7 (ecosystem)

Fixed versions

7.0.7

Fix

  • Fixed version 7.0.7
    pip install --upgrade notebook==7.0.7

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences