CVE-2024-37568: Authlib has algorithm confusion with asymmetric public keys

CVE-2024-37568 · Severity: low · CVSS 3.1 · Published 2024-06-09

lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)

Technologies: authlib (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-37568 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-37568 being exploited in the wild.
How severe is CVE-2024-37568?
Low severity, with a CVSS score of 3.1, published 9 June 2024.
Which products and versions are affected?
authlib (PyPI) ECOSYSTEM:introduced=0,fixed=1.3.1.
Is there a fix for CVE-2024-37568?
Yes. authlib (PyPI): upgrade to 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-37568?
Check whether you run authlib (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

  • authlib (PyPI): upgrade to 1.3.1 or later
    pip install "authlib>=1.3.1"

Affected products

  • authlib (PyPI) ECOSYSTEM:introduced=0,fixed=1.3.1

Identifiers

  • CVE-2024-37568
  • GHSA-5357-c2jx-v7qh
  • PYSEC-2024-52

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