GHSA-gcv9-6737-pjqw

Suggest an improvement
Source
https://github.com/advisories/GHSA-gcv9-6737-pjqw
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-gcv9-6737-pjqw/GHSA-gcv9-6737-pjqw.json
JSON Data
https://api.test.osv.dev/v1/vulns/GHSA-gcv9-6737-pjqw
Aliases
Related
Published
2022-01-27T16:24:26Z
Modified
2024-09-24T19:01:38.841340Z
Severity
  • 6.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N CVSS Calculator
  • 6.9 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
SSRF vulnerability in jupyter-server-proxy
Details

Impact

What kind of vulnerability is it? Server-Side Request Forgery ( SSRF )

Who is impacted? Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.

A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the allowed_hosts check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity.

Patches

Has the problem been patched? What versions should users upgrade to?

Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch

For more information

If you have any questions or comments about this advisory:

Database specific
{
    "nvd_published_at": "2022-01-25T14:15:00Z",
    "cwe_ids": [
        "CWE-918"
    ],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2022-01-25T20:57:43Z"
}
References

Affected packages

PyPI / jupyter-server-proxy

Package

Name
jupyter-server-proxy
View open source insights on deps.dev
Purl
pkg:pypi/jupyter-server-proxy

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
3.2.1

Affected versions

1.*

1.0b1
1.0b2
1.0b4
1.0b5
1.0b6
1.0b7
1.0b8
1.0b9
1.0
1.0.1
1.1.0
1.2.0
1.3.0
1.3.1
1.3.2
1.4.0
1.5.0
1.5.2
1.5.3
1.6.0

3.*

3.0.0rc1
3.0.0
3.0.1
3.0.2
3.1.0
3.2.0

Database specific

{
    "last_known_affected_version_range": "<= 3.2.0"
}