dbcve.org
FedoraOperating system · Fedoraproject

CVE-2024-22421

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-19
Fix available
A fix is available. Upgrade to 3.6.7 / 4.0.11 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Patch available

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 · unedited
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.

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

A detailed technical summary for this CVE is being prepared.

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
FedoraOperating system
Affected:= 39
JupyterlabApplication
Affected:< 3.6.7>= 4.0.0, < 4.0.11
NotebookApplication
Affected:>= 7.0.0, < 7.0.7

CVSS 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 · scoped
Upgrade available Upgrade to 3.6.7 / 4.0.11 / 7.0.7 or later
Fixed in 3.6.74.0.117.0.7
Vendor patch github.com →
Recommended fix High confidence

jupyterlab>=3.6.7, <4.0.0 (use 3.6.7) OR jupyterlab>=4.0.0, <4.1.0 (use 4.0.11) OR jupyterlab>=4.1.0 (use 4.1.0b2 or later), plus jupyter-server>=2.7.2

  1. 1. Check current JupyterLab version by running: `jupyter lab --version`
  2. 2. Check current jupyter-server version by running: `jupyter server list` or `pip show jupyter-server`
  3. 3. Upgrade JupyterLab to a patched version: `pip install --upgrade jupyterlab==4.0.11` (or 3.6.7 for the 3.x series)
  4. 4. Upgrade jupyter-server to version 2.7.2 or newer: `pip install --upgrade jupyter-server>=2.7.2`
  5. 5. Verify the upgrade was successful by checking: `jupyter lab --version` and `jupyter server version`
  6. 6. Restart the JupyterLab server to apply changes
Caveat Minimal risk; this is a security patch release. However, ensure any custom extensions are compatible with the new JupyterLab version.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22421 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22421 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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