# CVE-2022-24757: PYSEC-2022-179 - The Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications. Prior to version 1.

Source: https://junglewise.ai/threats/cve-2022-24757-insertion-of-sensitive-information-into-log-file-in-jupyter  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-03-23  
License: CC BY 4.0 with a link back

CVE-2022-24757 · Severity: low · CVSS 3.1 · Published 2022-03-23

The Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications. Prior to version 1.15.4, 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 Server version 1.15.4 contains a patch for this issue. There are currently no known workarounds.

Technologies: [jupyter-server (PyPI)](https://junglewise.ai/threats/technologies/pypi-jupyter-server). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2022-24757 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-24757 being exploited in the wild.

**How severe is CVE-2022-24757?** Low severity, with a CVSS score of 3.1, published 23 March 2022.

**Which products and versions are affected?** jupyter-server (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=a5683aca0b0e412672ac6218d09f74d44ca0de5a|ECOSYSTEM:introduced=0,fixed=1.15.4.

**Is there a fix for CVE-2022-24757?** Yes. jupyter-server (PyPI): upgrade to 1.15.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2022-24757?** Check whether you run jupyter-server (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- jupyter-server (PyPI): upgrade to 1.15.4 or later

  ```sh
  pip install "jupyter-server>=1.15.4"
  ```


## Affected products

- jupyter-server (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=a5683aca0b0e412672ac6218d09f74d44ca0de5a|ECOSYSTEM:introduced=0,fixed=1.15.4

## Identifiers

- CVE-2022-24757
- GHSA-p737-p57g-4cpr
- PYSEC-2022-179

## Related threats

- [Jupyter Server authorization bypass in kernel gateway handlers](https://junglewise.ai/threats/cve-2026-114135-jupyter-server-is-the-backend-for-jupyter-web-applications-from)
- [Jupyter Server token leakage in 5xx error logs](https://junglewise.ai/threats/cve-2026-86049-jupyter-server-token-leakage-in-5xx-error-logs)
- [Jupyter Server stored XSS in nbconvert handlers](https://junglewise.ai/threats/cve-2026-44727-jupyter-server-stored-xss-in-nbconvert-handlers)
- [Jupyter Jupyter Server CORS bypass via improper origin validation](https://junglewise.ai/threats/cve-2026-6657-jupyter-jupyter-server-cors-bypass-via-improper-origin-validation)
- [Jupyter jupyter-server path traversal in _get_os_path](https://junglewise.ai/threats/cve-2026-5422-jupyter-jupyter-server-path-traversal-in-get-os-path)