CVE-2023-25574 — jupyterhub-ltiauthenticat…
CRITICALCVE-2023-25574 is a critical-severity (CVSS 10) CWE-347 vulnerability in jupyterhub-ltiauthenticator. A fix is available for jupyterhub-ltiauthenticator — see the affected versions and patch details below.
JupyterHub's LTI13Authenticator: JWT signature not validated
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-25574.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
jupyterhub-ltiauthenticatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Only users that has configured a JupyterHub installation to use the authenticator class LTI13Authenticator are influenced.
LTI13Authenticator that was introduced in jupyterhub-ltiauthenticator 1.3.0 wasn't validating JWT signatures. This is believed to allow the LTI13Authenticator to authorize a forged request granting access to existing and new user identities.
Patches
None.
Workarounds
None.
References
- This code segment didn't validate a JWT signature.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | jupyterhub-ltiauthenticator | ≥ 1.3.0&&< 1.4.0 | 1.4.0pip install --upgrade 'jupyterhub-ltiauthenticator==1.4.0' |
Affected Products
lti jupyterhub authenticatorjupyterDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jupyterhub-ltiauthenticator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jupyterhub-ltiauthenticator to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-25574 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2023-25574 in your dependencies?
Find it across PyPI, including transitive dependencies.