Session hijacking via full-header error logging
Published Mar 31, 2022 · Updated Apr 23, 2025
Sensitive-data logging in Project Jupyter Jupyter Notebook before 6.4.10 allows local users to read authentication cookies from server logs. The notebook/log.py log_request function serializes every request header when most 5xx responses occur instead of limiting output to nonsensitive fields. Reading the server log does not require root access; a local user who can induce an error can recover a session cookie and access the server.
Summary
What happened
Sensitive-data logging in Project Jupyter Jupyter Notebook before 6.4.10 allows local users to read authentication cookies from server logs. The notebook/log.py log_request function serializes every request header when most 5xx responses occur instead of limiting output to nonsensitive fields. Reading the server log does not require root access; a local user who can induce an error can recover a session cookie and access the server.
The record
- CVE
- CVE-2022-24758
- Published
- Mar 31, 2022
- Updated
- Apr 23, 2025
- Vendor
- Project Jupyter
- Product
- Jupyter Notebook
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.4.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo