CVE-2022-21697: SSRF vulnerability in jupyter-server-proxy
Summary
CVE-2022-21697: SSRF vulnerability in jupyter-server-proxy. Affects jupyter-server-proxy versions < 3.2.1. Fixed in 3.2.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Jupyter Server Proxy is a package that allows users to proxy web applications running on Jupyter servers. It enables users to access and interact with these applications through the Jupyter Notebook interface. The package is commonly used by users deploying Jupyter Server or Notebook with the jupyter-proxy-server extension enabled. This vulnerability specifically affects versions up to 3.2.0 of the jupyter-server-proxy package.
Vulnerability Detail
The vulnerability identified in this advisory is a Server-Side Request Forgery (SSRF) vulnerability. It arises from a lack of input validation, which allows authenticated clients to proxy requests to other hosts, bypassing the allowed_hosts check. Although authentication is required to exploit this vulnerability, it is considered low to moderate severity because authenticated clients already have permissions to make similar requests via kernel or terminal execution.
How To Fix
Minimum fixed version
3.2.1
This is the first release that contains the fix.
pip install --upgrade "jupyter-server-proxy==3.2.1"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
In conclusion, the jupyter-server-proxy package is affected by a Server-Side Request Forgery (SSRF) vulnerability. Users are advised to upgrade to version 3.2.1 or apply the provided patch to mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for jupyter-server-proxy →
FAQ
Any user deploying Jupyter Server or Notebook with the jupyter-proxy-server extension enabled is impacted by this vulnerability.
The severity of this vulnerability is considered low to moderate.
The impact of this vulnerability is that authenticated clients can proxy requests to other hosts, bypassing the allowed_hosts check.
Yes, the vulnerability has been patched in version 3.2.1 of the jupyter-server-proxy package.
For more information, you can visit the Jupyter forum https://discourse.jupyter.org or email the Jupyter security team at security@ipython.org.
References
Related vulnerabilities
Recent vulnerabilities recorded for jupyter-server-proxy.
