pysec-2024-236
Vulnerability from pysec
Published
2024-06-11 22:15
Modified
2025-02-26 23:22
Severity ?
6.1 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.

Impacted products
Name purl
jupyter-server-proxy pkg:pypi/jupyter-server-proxy
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "jupyter-server-proxy",
            purl: "pkg:pypi/jupyter-server-proxy",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "7abc9dc5bbb0b4b440548a5375261b8b8192fc22",
                  },
                  {
                     fixed: "ff78128087e73fb9d0909e1366f8bf051e8ea878",
                  },
                  {
                     fixed: "7abc9dc5bbb0b4b440548a5375261b8b8192fc22",
                  },
                  {
                     fixed: "ff78128087e73fb9d0909e1366f8bf051e8ea878",
                  },
               ],
               repo: "https://github.com/jupyterhub/jupyter-server-proxy",
               type: "GIT",
            },
            {
               events: [
                  {
                     introduced: "3.0.0",
                  },
                  {
                     fixed: "3.2.4",
                  },
                  {
                     introduced: "4.1.2",
                  },
                  {
                     fixed: "4.2.0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "3.0.0",
            "3.0.1",
            "3.0.2",
            "3.1.0",
            "3.2.0",
            "3.2.1",
            "3.2.2",
            "3.2.3",
            "4.1.2",
         ],
      },
   ],
   aliases: [
      "CVE-2024-35225",
   ],
   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.",
   id: "PYSEC-2024-236",
   modified: "2025-02-26T23:22:41.524251+00:00",
   published: "2024-06-11T22:15:09+00:00",
   references: [
      {
         type: "ADVISORY",
         url: "https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-fvcq-4x64-hqxr",
      },
      {
         type: "FIX",
         url: "https://github.com/jupyterhub/jupyter-server-proxy/commit/7abc9dc5bbb0b4b440548a5375261b8b8192fc22",
      },
      {
         type: "FIX",
         url: "https://github.com/jupyterhub/jupyter-server-proxy/commit/ff78128087e73fb9d0909e1366f8bf051e8ea878",
      },
      {
         type: "WEB",
         url: "https://github.com/jupyterhub/jupyter-server-proxy/blob/62a290f08750f7ae55a0c29ca339c9a39a7b2a7b/jupyter_server_proxy/handlers.py#L328",
      },
   ],
   related: [
      "GHSA-fvcq-4x64-hqxr",
      "GHSA-fvcq-4x64-hqxr",
   ],
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.