← Back
CVE-2023-25574
Vulnerability in jupyterhub-ltiauthenticator (CVE-2023-25574)
Summary
vulnerability in jupyterhub-ltiauthenticator (CVE-2023-25574). Successful exploitation can lead to full system takeover. Exploitable via ``LTI13Authenticator``. Mitigation: upgrade to `1.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-25574** has been found in jupyterhub-ltiauthenticator.
Attackers can target a specific entry point like ``LTI13Authenticator`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade jupyterhub-ltiauthenticator to **1.4.0** or later.
If unsure, ask your IT team or search "jupyterhub-ltiauthenticator CVE-2023-25574" on the vendor's site.
CVE-2023-25574 (jupyterhub-ltiauthenticator) — CWE-347 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `LTI13Authenticator`
Patched: `1.4.0` — 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-347) exists in jupyterhub-ltiauthenticator. Attackers reach the vulnerable code path via ``LTI13Authenticator`` without authentication.
📍 Affected scope
jupyterhub-ltiauthenticator — . Attack surface: `LTI13Authenticator`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.4.0**.
🛡️ 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 'jupyterhub-ltiauthenticator' .` 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 'jupyterhub-ltiauthenticator' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyterhub-ltiauthenticator` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jupyterhub-ltiauthenticator to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
jupyterhub-ltiauthenticator
[{"type":"ECOSYSTEM","events":[{"introduced":"1.3.0"},{"fixed":"1.4.0"}]}]
pip
jupyterhub-ltiauthenticator
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/25xxx/CVE-2023-25574.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-25574
- package https://github.com/jupyterhub/ltiauthenticator
- web https://github.com/jupyterhub/ltiauthenticator/blob/3feec2e81b9d3b0ad6b58ab4226af640833039f3/ltiauthenticator/lti13/validator.py#L122-L164
- web https://github.com/jupyterhub/ltiauthenticator/blob/main/CHANGELOG.md#140---2023-03-01
- web https://github.com/jupyterhub/ltiauthenticator/security/advisories/GHSA-mcgx-2gcr-p3hp
- web https://github.com/pypa/advisory-database/tree/main/vulns/jupyterhub-ltiauthenticator/PYSEC-2025-120.yaml
- web https://github.com/advisories/GHSA-mcgx-2gcr-p3hp