jupyterhub jupyter-server-proxy up to 3.2.3/4.2.0 /proxy host cross site scripting

Summaryinfo

A vulnerability marked as problematic has been reported in jupyterhub jupyter-server-proxy up to 3.2.3/4.2.0. Impacted is an unknown function of the file /proxy. The manipulation of the argument host leads to cross site scripting. This vulnerability is uniquely identified as CVE-2024-35225. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in jupyterhub jupyter-server-proxy up to 3.2.3/4.2.0 and classified as problematic. This issue affects an unknown code of the file /proxy. The manipulation of the argument host with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

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/`. 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/`, 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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-35225 since 05/14/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 3.2.4 or 4.2.0 eliminates this vulnerability. Applying the patch 7abc9dc5bbb0b4b440548a5375261b8b8192fc22 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Firewall Software

Vendor

• jupyterhub

Name

• jupyter-server-proxy

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 4.0
• 4.1
• 4.2.0

License

• open-source

Website

• Product: https://github.com/jupyterhub/jupyter-server-proxy/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion