Skip to content

Jupyter server Token bruteforcing

High severity GitHub Reviewed Published Jun 14, 2022 in jupyter-server/jupyter_server • Updated Oct 26, 2023

Package

pip jupyter-server (pip)

Affected versions

>= 0, < 1.17.1
= 2.0.0a0

Patched versions

1.17.1
2.0.0a1

Description

Affects: Notebook and Lab between 6.4.0?(potentially earlier) and 6.4.11 (currently latest). Jupyter Server <=1.16.0. If I am correct about the responsible code it will affect Jupyter-Server 1.17.0 and 2.0.0a0 as well.
Description: If notebook server is started with a value of root_dir that contains the starting user's home directory, then the underlying REST API can be used to leak the access token assigned at start time by guessing/brute forcing the PID of the jupyter server. While this requires an authenticated user session, this url can be used from an xss payload (as in CVE-2021-32798) or from a hooked or otherwise compromised browser to leak this access token to a malicious third party. This token can be used along with the REST API to interact with Jupyter services/notebooks such as modifying or overwriting critical files, such as .bashrc or .ssh/authorized_keys, allowing a malicious user to read potentially sensitive data and possibly gain control of the impacted system.

References

@blink1073 blink1073 published to jupyter-server/jupyter_server Jun 14, 2022
Published by the National Vulnerability Database Jun 14, 2022
Published to the GitHub Advisory Database Jun 16, 2022
Reviewed Jun 16, 2022
Last updated Oct 26, 2023

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
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:H/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.104%
(43rd percentile)

Weaknesses

No CWEs

CVE ID

CVE-2022-29241

GHSA ID

GHSA-q874-g24w-4q9g

Source code

Credits

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