← Back
CVE-2024-28179
Vulnerability in jupyter-server-proxy (CVE-2024-28179)
Summary
vulnerability in jupyter-server-proxy (CVE-2024-28179). Successful exploitation can lead to full system takeover. Exploitable via ``jupyter_server``. Mitigation: upgrade to `764e499f61a87641916a7a427d4c4b1ac3f321a9, bead903b7c0354b6efd8b4cde94b89afab653e03, 3.2.3, 4.1.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-28179** has been found in jupyter-server-proxy.
Attackers can target a specific entry point like ``jupyter_server`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade jupyter-server-proxy to **764e499f61a87641916a7a427d4c4b1ac3f321a9, bead903b7c0354b6efd8b4cde94b89afab653e03, 3.2.3, 4.1.1** or later.
If unsure, ask your IT team or search "jupyter-server-proxy CVE-2024-28179" on the vendor's site.
CVE-2024-28179 (jupyter-server-proxy) — CWE-306 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `jupyter_server`
Patched: `764e499f61a87641916a7a427d4c4b1ac3f321a9, bead903b7c0354b6efd8b4cde94b89afab653e03, 3.2.3, 4.1.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-306) exists in jupyter-server-proxy. Attackers reach the vulnerable code path via ``jupyter_server`` without authentication.
📍 Affected scope
jupyter-server-proxy — . Attack surface: `jupyter_server`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **764e499f61a87641916a7a427d4c4b1ac3f321a9, bead903b7c0354b6efd8b4cde94b89afab653e03, 3.2.3, 4.1.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jupyter-server-proxy' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jupyter-server-proxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyter-server-proxy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jupyter-server-proxy to 764e499f61a87641916a7a427d4c4b1ac3f321a9, bead903b7c0354b6efd8b4cde94b89afab653e03, 3.2.3, 4.1.1ステージング環境で 764e499f61a87641916a7a427d4c4b1ac3f321a9, bead903b7c0354b6efd8b4cde94b89afab653e03, 3.2.3, 4.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
jupyter-server-proxy
[{"repo":"https:\/\/github.com\/jupyterhub\/jupyter-server-proxy","type":"GIT","events":[{"introduced":"0"},{"fixed":"764e499f61a87641916a7a427d4c4b1ac3f321a9"},{"fixed":"bead903b7c0354b6efd8b4cde94b89afab653e03"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3"},{"introduced":"4.0.0"},{"fixed":"4.1.1"}]}]
References
- advisory https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-w3vc-fx9p-wp4v
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-28179
- advisory https://github.com/advisories/GHSA-w3vc-fx9p-wp4v
- package https://github.com/jupyterhub/jupyter-server-proxy
- patch https://github.com/jupyterhub/jupyter-server-proxy/commit/764e499f61a87641916a7a427d4c4b1ac3f321a9
- patch https://github.com/jupyterhub/jupyter-server-proxy/commit/bead903b7c0354b6efd8b4cde94b89afab653e03
- web https://github.com/jupyterhub/jupyter-server-proxy/blob/9b624c4d9507176334b46a85d94a4aa3bcd29bed/jupyter_server_proxy/handlers.py#L433
- web https://github.com/pypa/advisory-database/tree/main/vulns/jupyter-server-proxy/PYSEC-2024-234.yaml