Skip to content

Insertion of Sensitive Information into Log File in Jupyter notebook

High severity GitHub Reviewed Published Mar 22, 2022 in jupyter-server/jupyter_server • Updated Jan 27, 2023

Package

pip jupyter-server (pip)

Affected versions

< 1.15.4

Patched versions

1.15.4

Description

Impact

What kind of vulnerability is it?

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.

Patches

Has the problem been patched? What versions should users upgrade to?

Upgrade to Jupyter Server version 1.15.4

For more information

If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.

Credit: @3coins for reporting. Thank you!

References

@Zsailer Zsailer published to jupyter-server/jupyter_server Mar 22, 2022
Published by the National Vulnerability Database Mar 23, 2022
Published to the GitHub Advisory Database Mar 25, 2022
Reviewed Mar 25, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.135%
(50th percentile)

Weaknesses

CVE ID

CVE-2022-24757

GHSA ID

GHSA-p737-p57g-4cpr

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.