MediumGHSA-v7vq-3x77-87vgBIT-jupyter-base-notebook-2022-29238BIT-jupyter-notebook-2022-29238CVE-2022-29238PYSEC-2022-212

Token bruteforcing.

Published 16 Jun 2022 · Updated 6 Dec 2023

Is your project on an affected notebook?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<6.4.12
Fixed in
6.4.12
Update to the fixed version for your release line, for example:pip install 'notebook>=6.4.12'

Details

Impact

_What kind of vulnerability is it? Who is impacted?_

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.

Patches

_Has the problem been patched? What versions should users upgrade to?_

notebook 6.4.12

Workarounds

_Is there a way for users to fix or remediate the vulnerability without upgrading?_

  • Do not run the notebook server in a directory with hidden files, use subdirectories
  • Use a custom ContentsManager with additional checks for self.is_hidden(path) prior to completing actions

References

_Are there any links users can visit to find out more?_

For more information

If you have any questions or comments about this advisory:

  • Open an issue in example link to repo
  • Email us at [example email address](mailto:example@example.com)

Is GHSA-v7vq-3x77-87vg in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected notebook, and gives you the command that fixes it.

More advisories for notebook

  • MediumCVE-2026-102832JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked · 15 Oct 2026
  • HighCVE-2026-102831JupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboard · 1 Oct 2026
  • HighCVE-2026-42557JupyterLab's command linker attributes in HTML enable one-click command execution from untrusted content · 6 May 2026
  • HighCVE-2026-40171Jupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSS · 30 Apr 2026
  • HighCVE-2024-43805HTML injection in Jupyter Notebook and JupyterLab leading to DOM Clobbering · 29 Aug 2024
  • HighCVE-2024-22421JupyterLab vulnerable to potential authentication and CSRF tokens leak · 19 Jan 2024
All 21 advisories for notebook

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.