CVE-2024-38371 Insufficient access control for OAuth2 Device Code flow in authentik

High 8.6 Published Updated

Attackers can bypass access controls in the OAuth2 Device Code flow to obtain tokens and access unauthorized applications in authentik.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2024-38371?

CVE-2024-38371 is a high-severity missing authorization vulnerability in goauthentik authentik, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

authentik is an open-source Identity Provider. Access restrictions assigned to an application were not checked when using the OAuth2 Device code flow. This could potentially allow users without the correct authorization to get OAuth tokens for an application and access it. This issue has been patched in version(s) 2024.6.0, 2024.2.4 and 2024.4.3.

Weakness: CWE-285, CWE-284

Which versions are affected by CVE-2024-38371?

1 open source package ship an affected version, including authentik. It affects 1 product.

PackageAffectedFixed in
authentik BitnamiAll versions2024.6.0

Products include Goauthentik Authentik.

How do I fix CVE-2024-38371?

Upgrade authentik to 2024.6.0 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2024-38371 being exploited?

There is no known exploitation of CVE-2024-38371 in the wild and no public exploit code.

Sources

Also known as BIT-authentik-2024-38371, GHSA-jq3m-37m7-gp45.

Is CVE-2024-38371 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free