jupyter-server
Affected
- introduced
0, fixed1.17.1(ecosystem)
Fixed versions
1.17.1
Fix
- Fixed version
1.17.1pip install --upgrade jupyter-server==1.17.1
Advisory
Also known as: CVE-2022-29241, PYSEC-2022-211
Jupyter server Token bruteforcing
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.
High Basis: The source's own band: HIGH
0, fixed 1.17.1 (ecosystem)1.17.1
1.17.1pip install --upgrade jupyter-server==1.17.12.0.0a0, fixed 2.0.0a1 (ecosystem)2.0.0a1
2.0.0a1pip install --upgrade jupyter-server==2.0.0a1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0