CVE-2024-37568

Authlib broken access control

7.5 HIGHPublic exploitEPSS 0.38%

Published9 Jun 2024

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.)

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityNone

IntegrityHigh

AvailabilityNone

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

Affected products

Authlib< 1.3.1

Remediation

Fixed in

Authlib≥ 1.3.1

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-37568 being actively exploited?

CVE-2024-37568 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.38%.

How severe is CVE-2024-37568?

CVE-2024-37568 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.38% probability of exploitation.

Which products are affected by CVE-2024-37568?

Affected products include Authlib.

How do I fix CVE-2024-37568?

Upgrade affected software to a fixed version, for example Authlib 1.3.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-37568 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.