jupyter-server-proxy
Affected
- introduced
0, fixed3.2.1(ecosystem)
Fixed versions
3.2.1
Fix
- Fixed version
3.2.1pip install --upgrade jupyter-server-proxy==3.2.1
Advisory
Also known as: CVE-2022-21697, PYSEC-2022-16
SSRF vulnerability in jupyter-server-proxy
Impact
What kind of vulnerability is it? Server-Side Request Forgery ( SSRF )
Who is impacted? Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.
A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the allowed_hosts check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity.
Patches
_Has the problem been patched? What versions should users upgrade to?_
Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch
For more information
If you have any questions or comments about this advisory:
Medium Basis: The source's own band: MODERATE
0, fixed 3.2.1 (ecosystem)3.2.1
3.2.1pip install --upgrade jupyter-server-proxy==3.2.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0