BIT-authentik-2024-52289

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/authentik/BIT-authentik-2024-52289.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-authentik-2024-52289
Aliases
Published
2026-04-16T23:36:22Z
Modified
2026-09-10T16:01:08Z
Summary
authentik has an insecure default configuration for OAuth2 Redirect URIs
Details

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

Database specific 
{
    "cpes": [
        "cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:go:*:*"
    ],
    "severity": "Critical"
}
References

Affected packages

Bitnami / authentik

Package

Name
authentik
Purl
pkg:bitnami/authentik

Severity

  • 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
2024.8.5
Introduced
2024.10.0
Fixed
2024.10.3

Database specific

source 
"https://github.com/bitnami/vulndb/tree/main/data/authentik/BIT-authentik-2024-52289.json"