CVE-2024-52289: authentik has an insecure default configuration for OAuth2 Redirect URIs
authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx comparison. When no Redirect URIs are configured in a provider, authentik will automatically use the first redirecturi value received as an allowed redirect URI, without escaping characters that have a special meaning in RegEx. Similarly, the documentation did not take this into consideration either. Given a provider with the Redirect URIs set to https://foo.example.com, an attacker can register a domain fooaexample.com, and it will correctly pass validation. authentik 2024.8.5 and 2024.10.3 fix this issue. As a workaround, When configuring OAuth2 providers, make sure to escape any wildcard characters that are not intended to function as a wildcard, for example replace . with \..
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-52289?
CVE-2024-52289 is classified as a medium severity vulnerability due to the improper handling of redirect URIs.
How do I fix CVE-2024-52289?
To mitigate CVE-2024-52289, ensure that you configure explicit redirect URIs for your OAuth2 provider in authentik.
Which versions of authentik are affected by CVE-2024-52289?
CVE-2024-52289 affects authentik versions from 2024.8.5 to 2024.10.3.
What is the nature of the vulnerability in CVE-2024-52289?
CVE-2024-52289 is caused by the use of a RegEx comparison to check redirect URIs, leading to potential unauthorized access.
Is there a workaround for CVE-2024-52289?
A temporary workaround for CVE-2024-52289 is to manually specify all redirect URIs in your authentik OAuth2 provider settings.