CVE-2024-52289 json
authentik has an insecure default configuration for OAuth2 Redirect URIs
published 2024-11-21 23 mo ago modified 2026-09-10 59 d ago also BIT-authentik-2024-52289 , EUVD-2024-45991 , GHSA-3q5w-6m3x-64gj
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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 redirect_uri 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 `\.`.
Patch / fix
- bitnami authentik 2024.8.5, 2024.10.3
- goauthentik authentik 2024.8.5, 2024.10.3
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 23 mo ago
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H |
| CNA | 4.0 | 7.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | authentik | <2024.8.5 >=2024.10.0, <2024.10.3 |
2024.8.5 2024.10.3 |
Affected products
- goauthentik authentik
Classification
- Weakness
-
- CWE-185 Incorrect Regular Expression
References
-
github.com
/goauthentik/authentik/commit/85bb638243c8d7ea42ddd3b15b3f51a90d2b8c54
patch
-
github.com
/goauthentik/authentik/security/advisories/GHSA-3q5w-6m3x-64gj
vendor-advisory, advisory
-
vicarius.io
/vsociety/posts/cve-2024-52289-detect-authentik-vulnerability
web
-
vicarius.io
/vsociety/posts/cve-2024-52289-mitigate-authentik-vulnerability
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-52289
web
Sources
- CVE List CVE-2024-52289
- NVD CVE-2024-52289
- OSV BIT-authentik-2024-52289
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.