CVE-2024-22421: Potential authentication and CSRF tokens leak in JupyterLab

Published Jan 19, 2024
·
Updated

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.

Other sources

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.

NVD

Affected Software

7 affected componentsFixes available
pip/notebook>=7.0.0<=7.0.6
7.0.7
pip/jupyterlab<=3.6.6
3.6.7
pip/jupyterlab>=4.0.0<=4.0.10
4.0.11
jupyter JupyterLab<3.6.7
jupyter JupyterLab>=4.0.0<4.0.11
jupyter notebook>=7.0.0<7.0.7
Fedoraproject Fedora=39

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/notebook to a version that resolves this vulnerability.

    Fixed in 7.0.7
  2. Upgrade

    Upgrade pip/jupyterlab to a version that resolves this vulnerability.

    Fixed in 3.6.7
  3. Upgrade

    Upgrade pip/jupyterlab to a version that resolves this vulnerability.

    Fixed in 4.0.11
  4. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.1.0b2
  5. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.0.11
  6. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 3.6.7
  7. Upgrade

    Upgrade jupyter-server to a version that resolves this vulnerability.

    Fixed in 2.7.2
  8. Compensating control

    Ensure users do not click malicious links when running JupyterLab with older jupyter-server versions, as token exposure (Authorization and XSRFToken) can occur via a malicious link.

Event History

Jan 19, 2024
Advisory Published
via GitHub·08:28 PM
CVE Published
via MITRE·08:45 PM
Data Sourced
via MITRE·08:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-22421?

CVE-2024-22421 is considered a high severity vulnerability due to the potential exposure of users' sensitive tokens.

2

How do I fix CVE-2024-22421?

To fix CVE-2024-22421, upgrade to JupyterLab versions 4.1.0b2, 4.0.11, or 3.6.7.

3

Who is affected by CVE-2024-22421?

Users of JupyterLab using affected older versions of the jupyter-server are at risk for CVE-2024-22421.

4

What does CVE-2024-22421 exploit?

CVE-2024-22421 exploits vulnerabilities in older versions of JupyterLab when users click on malicious links.

5

Is there a workaround for CVE-2024-22421?

There are no effective workarounds for CVE-2024-22421, and updating is the recommended action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203