CVE-2024-28179

Jupyter Server Proxy's Websocket Proxying does not require authentication

Published Mar 20, 2024 CVSS 3.1 · 9.1 Critical EPSS 1.0% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-1020 Jupyter Server Proxy's Websocket Proxying does not require authentication
Github GHSA Github GHSA GHSA-w3vc-fx9p-wp4v Jupyter Server Proxy's Websocket Proxying does not require authentication
History
Type Values Removed Values Added
First Time appeared Jupyter
Jupyter jupyter Server Proxy
CPEs cpe:2.3:a:jupyter:jupyter_server_proxy:*:*:*:*:*:*:*:*
Vendors & Products Jupyter
Jupyter jupyter Server Proxy
Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 2, 2024, 12:48 AM
Reserved
Mar 6, 2024, 5:35 PM
Status
Analyzed
Published
Mar 20, 2024, 8:15 PM
Modified
Jun 17, 2026, 7:21 AM