Skip to content

JupyterLab vulnerable to potential authentication and CSRF tokens leak

High severity GitHub Reviewed Published Jan 19, 2024 in jupyterlab/jupyterlab • Updated Feb 10, 2024

Package

pip jupyterlab (pip)

Affected versions

>= 4.0.0, <= 4.0.10
<= 3.6.6

Patched versions

4.0.11
3.6.7
pip notebook (pip)
>= 7.0.0, <= 7.0.6
7.0.7

Description

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.

References

@krassowski krassowski published to jupyterlab/jupyterlab Jan 19, 2024
Published to the GitHub Advisory Database Jan 19, 2024
Reviewed Jan 19, 2024
Published by the National Vulnerability Database Jan 19, 2024
Last updated Feb 10, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

EPSS score

0.068%
(32nd percentile)

Weaknesses

CVE ID

CVE-2024-22421

GHSA ID

GHSA-44cc-43rp-5947

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.