Authenticated path disclosure via JSON error tracebacks
Published Dec 4, 2023 · Updated Feb 13, 2025
Information disclosure in Jupyter Server before 2.11.2 allows remote authenticated users to obtain local filesystem paths. BaseHandler.write_error and the kernel restart handler serialize formatted exception tracebacks into JSON error responses instead of suppressing them. An authenticated API request must reach an unhandled error, and the disclosed paths have limited confidentiality impact because the requester already has code-execution rights in the same environment.
Summary
What happened
Information disclosure in Jupyter Server before 2.11.2 allows remote authenticated users to obtain local filesystem paths. BaseHandler.write_error and the kernel restart handler serialize formatted exception tracebacks into JSON error responses instead of suppressing them. An authenticated API request must reach an unhandled error, and the disclosed paths have limited confidentiality impact because the requester already has code-execution rights in the same environment.
The record
- CVE
- CVE-2023-49080
- Published
- Dec 4, 2023
- Updated
- Feb 13, 2025
- Vendor
- Project Jupyter
- Product
- Jupyter Server
- Classifications
- CWE-209, T1083
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=< 2.11.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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