CVE-2024-28179
CWE-306Published: March 20, 2024· Updated: Jun 17, 2026
Official 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.
Risk Analysis
Jupyter Server Proxy fails to properly authenticate websocket connections, allowing unauthenticated remote attackers to access websocket endpoints. This can lead to arbitrary code execution, making it a critical security concern for affected Jupyter instances.
No public exploit is known, and the vulnerability is not in the CISA KEV catalog.
Upgrade to Jupyter Server Proxy version 3.2.3 or 4.1.1 or later.
Technical Analysis
CVE-2024-28179 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.
The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.
A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 9.8.
CVSS v3.1 Vector Breakdown
Affected Vendors & Products
Exploit & PoC Resources
Official Patches & Advisories
All References (8)
Quick Facts
Related CVEs (CWE-306)
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2024-28179 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts