Unauthenticated file access via unprotected LSP endpoints
Published Jan 18, 2024 · Updated Sep 10, 2024
Missing authentication in JupyterLab LSP before 2.2.2 allows remote attackers to read or modify files outside the Jupyter root. The server extension leaves its REST and WebSocket handlers unprotected and passes attacker-controlled file URIs to the shadow-document filesystem without checking path containment. Exploitation requires a Jupyter Server reachable from an untrusted network and process permissions that permit access beyond the configured root.
Summary
What happened
Missing authentication in JupyterLab LSP before 2.2.2 allows remote attackers to read or modify files outside the Jupyter root. The server extension leaves its REST and WebSocket handlers unprotected and passes attacker-controlled file URIs to the shadow-document filesystem without checking path containment. Exploitation requires a Jupyter Server reachable from an untrusted network and process permissions that permit access beyond the configured root.
The record
- CVE
- CVE-2024-22415
- Published
- Jan 18, 2024
- Updated
- Sep 10, 2024
- Vendor
- Jupyter LSP
- Product
- JupyterLab LSP
- Classifications
- CWE-22, CWE-23, CWE-306, CWE-284, CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2024CVE publishedPublication date reported by the CVE source.
- Sep 10, 2024Record 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.2.2
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