CVE-2024-35225

Jupyter Server Proxy cross-site scripting (XSS)

9.6 CRITICALEPSS 0.45%

Published11 Jun 2024

Description

Jupyter Server Proxy allows users to run arbitrary external processes alongside their notebook server and provide authenticated web access to them. Versions of 3.x prior to 3.2.4 and 4.x prior to 4.2.0 have a reflected cross-site scripting (XSS) issue. The `/proxy` endpoint accepts a `host` path segment in the format `/proxy/<host>`. When this endpoint is called with an invalid `host` value, `jupyter-server-proxy` replies with a response that includes the value of `host`, without sanitization [2]. A third-party actor can leverage this by sending a phishing link with an invalid `host` value containing custom JavaScript to a user. When the user clicks this phishing link, the browser renders the response of `GET /proxy/<host>`, which runs the custom JavaScript contained in `host` set by the actor. As any arbitrary JavaScript can be run after the user clicks on a phishing link, this issue permits extensive access to the user's JupyterLab instance for an actor. Patches are included in versions 4.2.0 and 3.2.4. As a workaround, server operators who are unable to upgrade can disable the `jupyter-server-proxy` extension.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Jupyter Server Proxy≥ 3.0.0 < 3.2.4 · ≥ 4.1.2 < 4.2.0

Remediation

Fixed in

Jupyter Server Proxy≥ 3.2.4

Frequently asked

Is CVE-2024-35225 being actively exploited?

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

How severe is CVE-2024-35225?

CVE-2024-35225 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.45% probability of exploitation.

Which products are affected by CVE-2024-35225?

Affected products include Jupyter Server Proxy.

How do I fix CVE-2024-35225?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-35225 against the real software inventory on every managed device, every day. 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 works Book a demo

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