dbcve.org
Lti Jupyterhub AuthenticatorApplication · Jupyter

CVE-2023-25574

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
`jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI). 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. Only users that has configured a JupyterHub installation to use the authenticator class `LTI13Authenticator` are affected. `jupyterhub-ltiauthenticator` version 1.4.0 removes LTI13Authenticator to address the issue. No known workarounds are available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LTI13Authenticator class in jupyterhub-ltiauthenticator versions 1.3.0 through 1.4.0 fails to validate JWT signatures on incoming LTI 1.3 requests, allowing attackers to forge authentication tokens and gain unauthorized access to JupyterHub instances.

MitigationUpgrade to jupyterhub-ltiauthenticator version 1.4.0 or later, which removes the vulnerable LTI13Authenticator class entirely. Users requiring LTI 1.3 authentication will need to migrate to an alternative solution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Lti Jupyterhub AuthenticatorApplication
Affected:= 1.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify jupyterhub-ltiauthenticator is installed
    Run 'pip show jupyterhub-ltiauthenticator' or check your environment's package manager for the installed package
    Affected if The package is not installed or not found in the environment
  2. Determine the installed version of jupyterhub-ltiauthenticator
    Run 'pip show jupyterhub-ltiauthenticator' and note the Version field, or check your requirements.txt/pipfile for the pinned version
    Affected if The installed version is 1.3.0 or 1.4.0 (or any version between 1.3.0 and 1.4.0 inclusive)
  3. Inspect JupyterHub configuration for LTI13Authenticator usage
    Examine your jupyterhub_config.py file for any instantiation of LTI13Authenticator, such as 'c.JupyterHub.authenticator_class = LTI13Authenticator' or similar LTI 1.3 related configuration
    Affected if LTI13Authenticator class is explicitly configured as the authenticator or imported in the configuration
  4. Check if LTI 1.3 authentication is enabled
    Review your JupyterHub configuration files for LTI 1.3 related settings such as 'lti13_', 'client_id', 'endpoint', or other LTI 1.3 specific parameters
    Affected if LTI 1.3 authentication is actively configured and the LTI13Authenticator class is being used

The environment is affected if jupyterhub-ltiauthenticator version 1.3.0 or 1.4.0 is installed AND the LTI13Authenticator class is being used for LTI 1.3 authentication in the JupyterHub configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to jupyterhub-ltiauthenticator version 1.4.0 or later, which removes the vulnerable LTI13Authenticator class entirely. Users requiring LTI 1.3 authentication will need to migrate to an alternative solution.

Recommended fix High confidence

1.4.0

  1. 1. Review your JupyterHub configuration to identify any use of the `LTI13Authenticator` class
  2. 2. Ensure you have a backup of your current configuration
  3. 3. Upgrade jupyterhub-ltiauthenticator to version 1.4.0 using your package manager (e.g., pip install jupyterhub-ltiauthenticator==1.4.0)
  4. 4. Verify your configuration does not reference LTI13Authenticator as it has been removed in this version
  5. 5. Restart JupyterHub services
  6. 6. Test that authentication works with your remaining authenticator configuration
Caveat Version 1.4.0 removes LTI13Authenticator entirely - users relying on LTI 1.3 authentication will lose that functionality and must reconfigure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lti Jupyterhub Authenticator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25574 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25574 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data