| Name | CVE-2024-37568 |
| Description | 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.) |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| python-authlib (PTS) | bullseye | 0.15.4-1 | vulnerable |
| bookworm | 1.2.0-1 | vulnerable |
| sid, trixie | 1.3.2-2 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| python-authlib | source | (unstable) | 1.3.1-1 | | | |
Notes
[bookworm] - python-authlib <no-dsa> (Minor issue)
[bullseye] - python-authlib <postponed> (Minor issue; can be fixed in next update)
https://github.com/lepture/authlib/issues/654
https://github.com/lepture/authlib/commit/3bea812acefebc9ee108aa24557be3ba8971daf1 (v1.3.1)