Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/jupyter-server-proxy@0.8.1 |
|---|
| Type | pypi |
|---|
| Namespace | |
|---|
| Name | jupyter-server-proxy |
|---|
| Version | 0.8.1 |
|---|
| Qualifiers |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | true |
|---|
| Next_non_vulnerable_version | 3.2.4 |
|---|
| Latest_non_vulnerable_version | 4.2.0 |
|---|
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-b4gr-1pah-dyfr |
| vulnerability_id |
VCID-b4gr-1pah-dyfr |
| summary |
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. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2024-35225, GHSA-fvcq-4x64-hqxr, PYSEC-2024-236
|
| risk_score |
4.5 |
| exploitability |
0.5 |
| weighted_severity |
9.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-b4gr-1pah-dyfr |
|
| 1 |
| url |
VCID-dyqk-xd6y-67a2 |
| vulnerability_id |
VCID-dyqk-xd6y-67a2 |
| summary |
Jupyter Server Proxy allows users to run arbitrary external processes alongside their Jupyter notebook servers and provides authenticated web access. Prior to versions 3.2.3 and 4.1.1, Jupyter Server Proxy did not check user authentication appropriately when proxying websockets, allowing unauthenticated access to anyone who had network access to the Jupyter server endpoint. This vulnerability can allow unauthenticated remote access to any websocket endpoint set up to be accessible via Jupyter Server Proxy. In many cases, this leads to remote unauthenticated arbitrary code execution, due to how affected instances use websockets. The websocket endpoints exposed by `jupyter_server` itself is not affected. Projects that do not rely on websockets are also not affected. Versions 3.2.3 and 4.1.1 contain a fix for this issue. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2024-28179, GHSA-w3vc-fx9p-wp4v, PYSEC-2024-234
|
| risk_score |
4.5 |
| exploitability |
0.5 |
| weighted_severity |
9.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-dyqk-xd6y-67a2 |
|
|
|---|
| Fixing_vulnerabilities |
|
|---|
| Risk_score | 4.5 |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/jupyter-server-proxy@0.8.1 |
|---|