Skip to content
Fencer Intel
high 7.5

CVE-2022-24758 json

Insertion of Sensitive Information into Log File affects Jupyter Notebook

published 4y ago modified 2mo ago also BIT-jupyter-base-notebook-2022-24758 , BIT-jupyter-notebook-2022-24758 , EUVD-2022-0163 , GHSA-m87f-39q9-6f55 , PYSEC-2022-180

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

The Jupyter notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.9, unauthorized actors can access sensitive information from server logs. Anytime a 5xx error is triggered, the auth cookie and other header values are recorded in Jupyter server logs by default. Considering these logs do not require root access, an attacker can monitor these logs, steal sensitive auth/cookie information, and gain access to the Jupyter server. Jupyter notebook version 6.4.x contains a patch for this issue. There are currently no known workarounds.

Patch / fix

  • pypi notebook 6.4.10
  • bitnami jupyter-base-notebook 6.4.10
  • bitnami jupyter-notebook 6.4.10
  • jupyter notebook 6.4.10
  • jupyter-notebook Debian 14, Debian 13, Debian 12 6.4.12-1

debian advisories DEBIAN-CVE-2022-24758

  • jupyter-notebook Ubuntu 18.04 LTS 5.2.2-1ubuntu0.1
  • jupyter-notebook Ubuntu 20.04 LTS 6.0.3-2ubuntu0.1
  • jupyter-notebook Ubuntu 22.04 LTS 6.4.8-1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2022-24758

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • jupyter-notebook Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 6.4.10-r0

alpine advisories ALPINE-CVE-2022-24758

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-24758 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi notebook
<6.4.10
6.4.10
bitnami jupyter-base-notebook
<6.4.10
6.4.10
bitnami jupyter-notebook
<6.4.10
6.4.10

Affected products

  • jupyter notebook

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.