CVE-2024-43805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedjupyterlab 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDOM Clobbering vulnerability in JupyterLab's Markdown preview functionality allows a malicious notebook or Markdown file to manipulate DOM properties, enabling attackers to access any data the victim has access to and perform arbitrary requests as the attacked user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.6.8>= 4.0.0, < 4.2.5>= 7.0.0, < 7.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Jupyter product and versionRun 'jupyter --version' or 'pip show jupyterlab' or 'pip show notebook' to see which product is installed and its version numberAffected if The installed version falls within < 3.6.8, >= 4.0.0 and < 4.2.5 for JupyterLab, or >= 7.0.0 and < 7.2.2 for Notebook
-
Check if JupyterLab markdownviewer-extension is enabledRun 'jupyter labextension list' and look for '@jupyterlab/markdownviewer-extension' in the outputAffected if The extension is listed as enabled (not disabled or uninstalled)
-
Check if JupyterLab mathjax-extension is enabledRun 'jupyter labextension list' and look for '@jupyterlab/mathjax-extension' in the outputAffected if The extension is listed as enabled (not disabled or uninstalled)
-
Verify Notebook markdown preview capabilityFor Jupyter Notebook 7.x, check if the built-in markdown rendering is active by opening a notebook with untrusted Markdown contentAffected if Markdown files can be rendered in the Notebook interface (the vulnerability exists in the preview rendering path)
You are affected if you run JupyterLab versions 4.0.0 through 4.2.4, any version below 3.6.8, or Notebook versions 7.0.0 through 7.2.1, AND the markdownviewer-extension or mathjax-extension is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.6.84.2.57.2.2
Upgrade to JupyterLab v3.6.8+, v4.2.5+, or Notebook v7.2.2+; alternatively, disable the markdownviewer-extension and mathjax-extension plugins as temporary workarounds to eliminate the attack surface.
JupyterLab v3.6.8 or v4.2.5; Jupyter Notebook v7.2.2
- Identify whether you are using JupyterLab or Jupyter Notebook by running: jupyter --version or pip list | grep -i jupyter
- For JupyterLab users: Upgrade to v3.6.8 or v4.2.5 using: pip install --upgrade jupyterlab
- For Jupyter Notebook users: Upgrade to v7.2.2 using: pip install --upgrade notebook
- After upgrading, verify the installation: jupyter lab --version or jupyter notebook --version
- If immediate upgrade is not possible, disable vulnerable extensions as a mitigation by running: jupyter labextension disable @jupyterlab/markdownviewer-extension:plugin && jupyter labextension disable @jupyterlab/mathjax-extension:plugin && jupyter labextension disable @jupyterlab/mathjax2-extension:plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data