File disclosure via missing XSRF check
Published Aug 28, 2023 · Updated Feb 13, 2025
Cross-site inclusion in Jupyter Server before 2.7.2 allows remote authenticated users to expose files through crafted /files/ requests. The default FileFindHandler.get path served files without calling check_xsrf_cookie(), so cross-site requests carrying browser credentials were not rejected. Exploitation requires an authenticated browser session and user interaction, and it can disclose files accessible to that server session or load an untrusted file in the Jupyter origin.
Summary
What happened
Cross-site inclusion in Jupyter Server before 2.7.2 allows remote authenticated users to expose files through crafted /files/ requests. The default FileFindHandler.get path served files without calling check_xsrf_cookie(), so cross-site requests carrying browser credentials were not rejected. Exploitation requires an authenticated browser session and user interaction, and it can disclose files accessible to that server session or load an untrusted file in the Jupyter origin.
The record
- CVE
- CVE-2023-40170
- Published
- Aug 28, 2023
- Updated
- Feb 13, 2025
- Vendor
- Project Jupyter
- Product
- Jupyter Server
- Classifications
- CWE-284, CWE-306, CWE-79, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 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.7.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