Most severe vulnerabilities for "jupyter lti jupyterhub authenticator"

Where

Sort:

Versions

1.3.0

pip/jupyterhub-ltiauthenticatorJupyterHub's LTI13Authenticator: JWT signature not validated

Risk 87

Severity

AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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.

1 / 2

Source: GitHub

First published (updated )

CVE-2023-25574

pip/jupyterhub-ltiauthenticatorLTI JupyterHub Authenticator: Unbounded Memory Growth via Nonce Storage (Denial of Service)

Risk 35

Severity

5.9

AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Summary

The LTI 1.1 validator stores OAuth nonces in a class-level dictionary that grows without bounds. Nonces are added before signature validation, so an attacker with knowledge of a valid consumer key can send repeated requests with unique nonces to gradually exhaust server memory, causing a denial of service.

Patches

- upgrade jupyterhub-litauthenticator to 1.6.3

1 / 2

Source: GitHub

First published (updated )

CVE-2026-34052

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.