Authenticated SSRF via userinfo-style proxy paths
Published Jan 25, 2022 · Updated Apr 23, 2025
SSRF in Jupyter Server Proxy before 3.2.1 allows remote authenticated users to send proxy requests to arbitrary network hosts. The proxy routes accept userinfo-style path text containing an at sign, validate the apparent host, and then build a request whose actual destination follows the at sign. The extension must be enabled and valid Jupyter credentials are required; reachable services can be read or modified, although those users can already issue requests through kernels or terminals.
Summary
What happened
SSRF in Jupyter Server Proxy before 3.2.1 allows remote authenticated users to send proxy requests to arbitrary network hosts. The proxy routes accept userinfo-style path text containing an at sign, validate the apparent host, and then build a request whose actual destination follows the at sign. The extension must be enabled and valid Jupyter credentials are required; reachable services can be read or modified, although those users can already issue requests through kernels or terminals.
The record
- CVE
- CVE-2022-21697
- Published
- Jan 25, 2022
- Updated
- Apr 23, 2025
- Vendor
- JupyterHub
- Product
- Jupyter Server Proxy
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 25, 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=< 3.2.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