CVE-2024-22420: Stored cross site scripting in Markdown Preview in JupyterLab

Published Jan 19, 2024
·
Updated

Impact

The vulnerability depends on user interaction by opening a malicious notebook with Markdown cells, or Markdown file using JupyterLab preview feature.

A malicious user can access any data that the attacked user has access to as well as perform arbitrary requests acting as the attacked user.

Patches

JupyterLab v4.0.11 was patched.

Workarounds

Users can either disable the table of contents extension by running:

bash jupyter labextension disable @jupyterlab/toc-extension:registry

References

Vulnerability reported 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. This vulnerability depends on user interaction by opening a malicious Markdown file using JupyterLab preview feature. A malicious user can access any data that the attacked user has access to as well as perform arbitrary requests acting as the attacked user. JupyterLab version 4.0.11 has been patched. Users are advised to upgrade. Users unable to upgrade should disable the table of contents extension.

NVD

Affected Software

5 affected componentsFixes available
pip/notebook>=7.0.0<=7.0.6
7.0.7
pip/jupyterlab>=4.0.0<=4.0.10
4.0.11
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 4.0.11
  3. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.0.11
  4. Configuration

    Disable the table of contents extension by running: jupyter labextension disable @jupyterlab/toc-extension:registry

    JupyterLab (table of contents extension @jupyterlab/toc-extension) labextension disable @jupyterlab/toc-extension:registry = disabled

Event History

Jan 19, 2024
Advisory Published
via GitHub·08:24 PM
CVE Published
via MITRE·08:49 PM
Data Sourced
via MITRE·08:49 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-22420?

CVE-2024-22420 is considered a high severity vulnerability as it allows attackers to access sensitive data by exploiting user interactions.

2

How do I fix CVE-2024-22420?

To fix CVE-2024-22420, upgrade the JupyterLab package to version 4.0.11 or later and the Notebook package to version 7.0.7 or later.

3

What is the impact of CVE-2024-22420?

The impact of CVE-2024-22420 includes unauthorized access to user data and the ability to perform arbitrary requests on behalf of the user.

4

Which software is affected by CVE-2024-22420?

CVE-2024-22420 affects JupyterLab versions from 4.0.0 to 4.0.10 and Notebook versions from 7.0.0 to 7.0.6.

5

What user action is required to trigger CVE-2024-22420?

CVE-2024-22420 requires user interaction, specifically opening a malicious notebook or Markdown file in JupyterLab.

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