Log in Start free

Vulnerability · Published Mar 20, 2024 · Assigned by GitHub_M

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

Critical 9.1

In plain English

A critical-severity missing authentication in jupyter-server-proxy from jupyterhub. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.0% (higher than 64% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.1Critical
Exploit odds (30 days)1.0%top 36.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPIjupyter-server-proxy4.1.1GHSA-w3vc-fx9p-wp4v
PyPIjupyter-server-proxy3.2.3GHSA-w3vc-fx9p-wp4v
PyPIjupyter-server-proxy3.2.3, 4.1.1PYSEC-2024-234

Affected products (as reported)

VendorProductVersions
jupyterhub jupyter-server-proxy >= 4.0.0, < 4.1.1< 3.2.3

Weakness: CWE-306 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

References