CVE-2022-29238 Forced Browsing in Jupyter Notebook
Authenticated users can access hidden files despite configuration restrictions, potentially exposing sensitive data if file names are guessable.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-29238?
CVE-2022-29238 is a medium-severity missing authorization vulnerability in jupyter notebook, published on 14 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Jupyter Notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.12, authenticated requests to the notebook server with `ContentsManager.allow_hidden = False` only prevented listing the contents of hidden directories, not accessing individual hidden files or files in hidden directories (i.e. hidden files were 'hidden' but not 'inaccessible'). This could lead to notebook configurations allowing authenticated access to files that may reasonably be expected to be disallowed. Because fully authenticated requests are required, this is of relatively low impact. But if a server's root directory contains sensitive files whose only protection from the server is being hidden (e.g. `~/.ssh` while serving $HOME), then any authenticated requests could access files if their names are guessable. Such contexts also necessarily have full access to the server and therefore execution permissions, which also generally grants access to all the same files. So this does not generally result in any privilege escalation or increase in information access, only an additional, unintended means by which the files could be accessed. Version 6.4.12 contains a patch for this issue. There are currently no known workarounds.
Weakness: CWE-425
Which versions are affected by CVE-2022-29238?
5 open source packages ship an affected version, including jupyter-base-notebook, jupyter-notebook and notebook. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
jupyter-base-notebook Bitnami | All versions | 6.4.12 |
jupyter-notebook Bitnami | All versions | 6.4.12 |
notebook PyPI | All versions | 6.4.12 |
notebook PyPI | All versions | 6.4.12 |
notebook PyPI | All versions | 6.4.12 |
Products include Jupyter Notebook.
How do I fix CVE-2022-29238?
Upgrade jupyter-base-notebook to 6.4.12 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-29238 being exploited?
There is no known exploitation of CVE-2022-29238 in the wild and no public exploit code.
Other vulnerabilities in jupyter notebook
- CVE-2021-32798 Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook
- CVE-2018-8768 Jupyter Notebook file bypasses sanitization, executes JavaScript
- CVE-2022-24758 Insertion of Sensitive Information into Log File affects Jupyter Notebook
- CVE-2019-10856 Jupyter Notebook open redirect vulnerability
- CVE-2018-19351 Jupyter Notebook XSS via untrusted notebooks
Sources
Also known as BIT-jupyter-base-notebook-2022-29238, BIT-jupyter-notebook-2022-29238, CLEANSTART-2026-IA17108, DEBIAN-CVE-2022-29238, GHSA-v7vq-3x77-87vg, PYSEC-2022-212 and 2 more.