Skip to content

LTI JupyterHub Authenticator does not properly validate JWT Signature

Critical severity GitHub Reviewed Published Feb 25, 2025 in jupyterhub/ltiauthenticator • Updated Feb 25, 2025

Package

pip jupyterhub-ltiauthenticator (pip)

Affected versions

= 1.3.0

Patched versions

1.4.0

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

References

@consideRatio consideRatio published to jupyterhub/ltiauthenticator Feb 25, 2025
Published by the National Vulnerability Database Feb 25, 2025
Published to the GitHub Advisory Database Feb 25, 2025
Reviewed Feb 25, 2025
Last updated Feb 25, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS score

Weaknesses

CVE ID

CVE-2023-25574

GHSA ID

GHSA-mcgx-2gcr-p3hp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.