Secuno
ENNL
Book demo

CVE-2024-28179

Jupyter Server Proxy vulnerability

9.0 CRITICALEPSS 1.03%
  1. Published20 Mar 2024

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Jupyter Server Proxy≥ 4.0.0 < 4.1.1 · < 3.2.3

Remediation

Fixed in
Jupyter Server Proxy≥ 4.1.1

Frequently asked

Is CVE-2024-28179 being actively exploited?

CVE-2024-28179 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.03%.

How severe is CVE-2024-28179?

CVE-2024-28179 has a CVSS 3.1 base score of 9.0, rated critical. EPSS estimates a 1.03% probability of exploitation.

Which products are affected by CVE-2024-28179?

Affected products include Jupyter Server Proxy.

How do I fix CVE-2024-28179?

Upgrade affected software to a fixed version, for example Jupyter Server Proxy 4.1.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-28179 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.