← Back
CVE-2024-37300
Authorization Flaw in oauthenticator (CVE-2024-37300)
Summary
vulnerability in oauthenticator (CVE-2024-37300). Confidential information can be exposed externally. Exploitable via ``GlobusOAuthenticator``. Mitigation: upgrade to `16.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-37300** has been found in oauthenticator.
Attackers can target a specific entry point like ``GlobusOAuthenticator`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade oauthenticator to **16.3.1** or later.
If unsure, ask your IT team or search "oauthenticator CVE-2024-37300" on the vendor's site.
CVE-2024-37300 (oauthenticator) — CWE-863 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `GlobusOAuthenticator` / `allow_all` / `identity_provider`
Patched: `16.3.1` — apply immediately
Workaround: Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.
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
**incorrect authorization** (CWE-863) exists in oauthenticator. Attackers reach the vulnerable code path via ``GlobusOAuthenticator`` without authentication.
📍 Affected scope
oauthenticator — . Attack surface: `GlobusOAuthenticator` / `allow_all` / `identity_provider`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **16.3.1**.
🛡️ Workaround
Workaround: Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'oauthenticator' .` 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 'oauthenticator' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `oauthenticator` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.パッチが適用されるまでの応急処置として、Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade oauthenticator to 16.3.1ステージング環境で 16.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
oauthenticator
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.3.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-37300
- advisory https://github.com/advisories/GHSA-gprj-3p75-f996
- package https://github.com/jupyterhub/oauthenticator
- package https://pypi.org/project/oauthenticator
- web https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-gprj-3p75-f996
- web https://github.com/jupyterhub/oauthenticator/commit/d1aea05fa89f2beae15ab0fa0b0d071030f79654
- web https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users