Advisory

PYSEC-2024-236

Also known as: CVE-2024-35225, GHSA-fvcq-4x64-hqxr

Summary

The record has no summary.

Details

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.

Severity

Medium Basis: CVSS v3 score 6.1, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Dates

Published
2024-06-11 22:15 UTC
Modified
2026-06-10 17:14 UTC

Affected packages and fixes

jupyter-server-proxy

PyPI · All systems

Affected

  • introduced 3.0.0, fixed 3.2.4, introduced 4.1.2, fixed 4.2.0 (ecosystem)

Fixed versions

3.2.4, 4.2.0

Fix

  • Fixed version 3.2.4
    pip install --upgrade jupyter-server-proxy==3.2.4
  • Fixed version 4.2.0
    pip install --upgrade jupyter-server-proxy==4.2.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences