Is CVE-2023-25574 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2023-25574 being exploited in the wild.

How severe is CVE-2023-25574?

Critical severity, with a CVSS score of 10, published 25 February 2025.

Which products and versions are affected?

jupyterhub-ltiauthenticator (PyPI) = 1.3.0, ECOSYSTEM:introduced=0,last_affected=1.3.0, ECOSYSTEM:introduced=1.3.0,fixed=1.4.0.

Is there a fix for CVE-2023-25574?

Yes. jupyterhub-ltiauthenticator (PyPI): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2023-25574 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2023-25574?

Check whether you run jupyterhub-ltiauthenticator (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2023-25574: JupyterHub LTI Authenticator JWT signature validation bypass

CVE-2023-25574 · Severity: critical · CVSS 10 · Published 2025-02-25

A security flaw in the JupyterHub LTI Authenticator allows unauthorized individuals to gain access to user accounts. This component is used to connect JupyterHub with learning management systems; because it fails to verify digital signatures, an attacker can forge login requests to impersonate existing users or create new ones. This could lead to a total compromise of the JupyterHub environment and unauthorized access to student or researcher data.

Vendors: PyPI.

Quick answers

Is CVE-2023-25574 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2023-25574 being exploited in the wild.
How severe is CVE-2023-25574?: Critical severity, with a CVSS score of 10, published 25 February 2025.
Which products and versions are affected?: jupyterhub-ltiauthenticator (PyPI) = 1.3.0, ECOSYSTEM:introduced=0,last_affected=1.3.0, ECOSYSTEM:introduced=1.3.0,fixed=1.4.0.
Is there a fix for CVE-2023-25574?: Yes. jupyterhub-ltiauthenticator (PyPI): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2023-25574 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2023-25574?: Check whether you run jupyterhub-ltiauthenticator (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

jupyterhub-ltiauthenticator (PyPI): upgrade to 1.4.0 or later
```
pip install "jupyterhub-ltiauthenticator>=1.4.0"
```

Technical details

The LTI13Authenticator class in jupyterhub-ltiauthenticator version 1.3.0 fails to perform cryptographic signature validation on JSON Web Tokens (JWT) received during the LTI 1.3 login flow. This vulnerability is located in the validator.py component. A remote, unauthenticated attacker can exploit this by sending a specially crafted, forged JWT to the authentication endpoint. Successful exploitation allows the attacker to bypass authentication entirely, granting them access to existing user identities or the ability to provision new ones. The issue is addressed in version 1.4.0.

Affected products

JupyterHub jupyterhub-ltiauthenticator 1.3.0

Identifiers

CVE-2023-25574
GHSA-mcgx-2gcr-p3hp
PYSEC-2025-120

Timeline

2023-03-01: patched: Version 1.4.0 released
2025-02-25: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.