First published: Tue Jan 25 2022(Updated: )
### 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: * Open a topic [on our forum](https://discourse.jupyter.org) * Email the Jupyter security team at [security@ipython.org](mailto:security@ipython.org)
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jupyter Jupyter Server Proxy | <3.2.1 | |
pip/jupyter-server-proxy | <=3.2.0 | 3.2.1 |
https://github.com/jupyterhub/jupyter-server-proxy/commit/fd31930bacd12188c448c886e0783529436b99eb
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-21697 is a vulnerability in Jupyter Server Proxy, a Jupyter notebook server extension, that allows for Server-Side Request Forgery (SSRF).
CVE-2022-21697 affects Jupyter Server Proxy version up to 3.2.1.
Server-Side Request Forgery (SSRF) is a vulnerability that allows an attacker to send crafted requests from a vulnerable server, potentially leading to unauthorized access or data exfiltration from internal systems.
The severity of CVE-2022-21697 is high, with a CVSS score of 7.1.
To fix CVE-2022-21697, update Jupyter Server Proxy to version 3.2.1 or higher.