CVE-2024-35225

{"id": "CVE-2024-35225", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.6, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 2.8}]}, "published": "2024-06-11T22:15:09.520", "references": [{"url": "https://github.com/jupyterhub/jupyter-server-proxy/blob/62a290f08750f7ae55a0c29ca339c9a39a7b2a7b/jupyter_server_proxy/handlers.py#L328", "source": "security-advisories@github.com"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/commit/7abc9dc5bbb0b4b440548a5375261b8b8192fc22", "source": "security-advisories@github.com"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/commit/ff78128087e73fb9d0909e1366f8bf051e8ea878", "source": "security-advisories@github.com"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-fvcq-4x64-hqxr", "source": "security-advisories@github.com"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/blob/62a290f08750f7ae55a0c29ca339c9a39a7b2a7b/jupyter_server_proxy/handlers.py#L328", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/commit/7abc9dc5bbb0b4b440548a5375261b8b8192fc22", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/commit/ff78128087e73fb9d0909e1366f8bf051e8ea878", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-fvcq-4x64-hqxr", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-79"}, {"lang": "en", "value": "CWE-116"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Jupyter Server Proxy permite a los usuarios ejecutar procesos externos arbitrarios junto con su servidor port\u00e1til y proporcionarles acceso web autenticado. Las versiones 3.x anteriores a 3.2.4 y 4.x anteriores a 4.2.0 tienen un problema de cross-site scripting (XSS) reflejado. El endpoint `/proxy` acepta un segmento de ruta `host` en el formato `/proxy/`. Cuando se llama a este endpoint con un valor de \"host\" no v\u00e1lido, \"jupyter-server-proxy\" responde con una respuesta que incluye el valor de \"host\", sin sanitizaci\u00f3n [2]. Un actor externo puede aprovechar esto enviando un enlace de phishing con un valor de \"host\" no v\u00e1lido que contenga JavaScript personalizado a un usuario. Cuando el usuario hace clic en este enlace de phishing, el navegador muestra la respuesta `GET /proxy/`, que ejecuta el JavaScript personalizado contenido en `host` establecido por el actor. Como se puede ejecutar cualquier JavaScript arbitrario despu\u00e9s de que el usuario hace clic en un enlace de phishing, este problema permite un acceso extenso a la instancia de JupyterLab del usuario para un actor. Los parches se incluyen en las versiones 4.2.0 y 3.2.4. Como workaround, los operadores de servidores que no puedan actualizar pueden desactivar la extensi\u00f3n `jupyter-server-proxy`."}], "lastModified": "2024-11-21T09:19:58.493", "sourceIdentifier": "security-advisories@github.com"}