CVE-2022-29241
Jupyter Server Access Token Leak
Description
Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications like Jupyter Notebook. Prior to version 1.17.1, 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 a cross-site scripting payload 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. This issue is patched in version 1.17.1.
INFO
Published Date :
June 14, 2022, 9:15 p.m.
Last Modified :
Nov. 21, 2024, 6:58 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.9
Exploitability Score :
2.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-29241.
| URL | Resource |
|---|---|
| https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g | Third Party Advisory |
| https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-29241 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-29241 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Jun. 24, 2022
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:L/Au:S/C:C/I:C/A:C) Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g No Types Assigned https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g Third Party Advisory Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:a:jupyter:jupyter_server:*:*:*:*:*:*:*:* versions up to (excluding) 1.17.0
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-29241 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-29241
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.10 }} -0.01%
score
0.41185
percentile