Categories
CVE-2024-43805

Cross-Site Scripting (XSS) in jupyterlab (CVE-2024-43805)

Summary

Cross-site scripting in jupyterlab (CVE-2024-43805). Confidential information can be exposed externally. Exploitable via allowNamedProperties. Mitigation: upgrade to 4.2.5 or later.

Original description

The description as published by the source.

jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. This 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. JupyterLab v3.6.8, v4.2.5 and Jupyter Notebook v7.2.2 have been patched to resolve this issue. Users are advised to upgrade. There is no workaround for the underlying DOM Clobbering susceptibility. However, select plugins can be disabled on deployments which cannot update in a timely fashion to minimise the risk. These are: 1. @jupyterlab/mathjax-extension:plugin - users will loose ability to preview mathematical equations. 2. @jupyterlab/markdownviewer-extension:plugin - users will loose ability to open Markdown previews. 3. @jupyterlab/mathjax2-extension:plugin (if installed with optional jupyterlab-mathjax2 package) - an older version of the mathjax plugin for JupyterLab 4.x. To disable these extensions run: jupyter labextension disable @jupyterlab/markdownviewer-extension:plugin && jupyter labextension disable @jupyterlab/mathjax-extension:plugin && jupyter labextension disable @jupyterlab/mathjax2-extension:plugin in bash.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-43805 has been found in jupyterlab.
Attackers can target a specific entry point like allowNamedProperties over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade jupyterlab to 4.2.5 or later.
If unsure, ask your IT team or search "jupyterlab CVE-2024-43805" on the vendor's site.

CVE-2024-43805 (jupyterlab) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: allowNamedProperties
Patched: 4.2.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in jupyterlab. Attackers reach the vulnerable code path via allowNamedProperties without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of jupyterlab. Attack surface: allowNamedProperties.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 4.2.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jupyterlab' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'jupyterlab' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jupyterlab を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade jupyterlab to 4.2.5

    ステージング環境で 4.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI jupyterlab
[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.2.5"}]}]
PyPI notebook
[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.0"},{"fixed":"7.2.2"}]}]
Bitnami jupyter-notebook
[{"type":"SEMVER","events":[{"introduced":"7.0.0"},{"fixed":"7.2.2"}]}]
Bitnami jupyter-base-notebook
[{"type":"SEMVER","events":[{"introduced":"7.0.0"}]}]
Bitnami jupyterlab
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.2.5"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details