Access-token disclosure via unchecked hidden-file paths
Published Jun 14, 2022 · Updated Apr 23, 2025
Information disclosure in Jupyter Server before 1.17.1 allows remote authenticated users to obtain the server access token via its REST API. The contents handlers resolve direct paths to hidden runtime files without applying hidden-path checks, so a guessed server PID filename reveals its token. Exposure requires a root directory containing the server user's home directory; the token permits reading or overwriting files through Jupyter services.
Summary
What happened
Information disclosure in Jupyter Server before 1.17.1 allows remote authenticated users to obtain the server access token via its REST API. The contents handlers resolve direct paths to hidden runtime files without applying hidden-path checks, so a guessed server PID filename reveals its token. Exposure requires a root directory containing the server user's home directory; the token permits reading or overwriting files through Jupyter services.
The record
- CVE
- CVE-2022-29241
- Published
- Jun 14, 2022
- Updated
- Apr 23, 2025
- Vendor
- Project Jupyter
- Product
- Jupyter Server
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 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=< 1.17.1
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