Vulnerability in jupyterhub (CVE-2021-41247)
Summary
Vulnerability in jupyterhub (CVE-2021-41247). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.0 or later.
Original description
The description as published by the source.
Impact
Users of JupyterLab with JupyterHub who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place.
Patches
Upgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the user environment that needs patching. There are no patches necessary in the Hub environment.
Workarounds
The only workaround is to make sure that only one JupyterLab tab is open when you log out.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41247 has been found in jupyterhub.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jupyterhub to 1.5.0 or later.
If unsure, ask your IT team or search "jupyterhub CVE-2021-41247" on the vendor's site.
CVE-2021-41247 (jupyterhub) — CWE-613
Attack vector: remote (network-reachable)
Patched: 1.5.0 — apply immediately
Workaround: The only workaround is to make sure that only one JupyterLab tab is open when you log out.
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.
A vulnerability (CWE-613) exists in jupyterhub.
Check the vendor advisory for the affected versions of jupyterhub.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.0.
Workaround: The only workaround is to make sure that only one JupyterLab tab is open when you log out.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jupyterhub' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jupyterhub' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jupyterhubを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
The only workaround is to make sure that only one JupyterLab tab is open when you log out.パッチが適用されるまでの応急処置として、The only workaround is to make sure that only one JupyterLab tab is open when you log out. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade jupyterhub to 1.5.0ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com