CVE-2024-37568: High severity Authlib Authlib vulnerability
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.)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/authlibto a version that resolves this vulnerability.Fixed in 1.3.1 - Upgrade
Upgrade
debian/python-authlibto a version that resolves this vulnerability.Fixed in 1.2.0-1+deb12u1 - Upgrade
Upgrade
debian/python-authlibto a version that resolves this vulnerability.Fixed in 1.3.1-1 - Upgrade
Upgrade
debian/python-authlibto a version that resolves this vulnerability.Fixed in 1.2.0-1+deb12u1Fixed in 1.2.0-1+deb12u2Fixed in 1.6.0-1+deb13u1Fixed in 1.9.1-1 - Upgrade
Upgrade
ubuntu/python-authlibto a version that resolves this vulnerability.Fixed in 0.15.5-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/python-authlibto a version that resolves this vulnerability.Fixed in 1.3.0-1ubuntu0.1~esm1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-37568?
CVE-2024-37568 is classified as a medium severity vulnerability due to potential HMAC verification risks with asymmetric public keys.
How do I fix CVE-2024-37568?
To fix CVE-2024-37568, upgrade Authlib to version 1.3.1 or later.
What type of attack does CVE-2024-37568 expose software to?
CVE-2024-37568 exposes software to risks of algorithm confusion attacks, allowing unauthorized HMAC verification.
Which versions of Authlib are affected by CVE-2024-37568?
Authlib versions prior to 1.3.1 are affected by CVE-2024-37568.
Is there a workaround for CVE-2024-37568 if I cannot upgrade?
A workaround for CVE-2024-37568 involves explicitly specifying the algorithm in the jwt.decode call.