CVE-2023-48228

See a problem?
Please try reporting it to the source first.

Source

https://cve.org/CVERecord?id=CVE-2023-48228

Import Source

https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-48228.json

JSON Data

https://api.test.osv.dev/v1/vulns/CVE-2023-48228

Aliases

BIT-authentik-2023-48228
GHSA-fm34-v8xq-f2c3

Published

2023-11-21T20:48:32.552Z

Modified

2026-05-14T03:52:42.173742104Z

Severity

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

Summary

OAuth2: PKCE can be fully circumvented

Details

authentik is an open-source identity provider. When initialising a oauth2 flow with a code_challenge and code_method (thus requesting PKCE), the single sign-on provider (authentik) must check if there is a matching and existing code_verifier during the token step. Prior to versions 2023.10.4 and 2023.8.5, authentik checks if the contents of code_verifier is matching only when it is provided. When it is left out completely, authentik simply accepts the token request with out it; even when the flow was started with a code_challenge. authentik 2023.8.5 and 2023.10.4 fix this issue.

Database specific

{
    "cna_assigner": "GitHub_M",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/48xxx/CVE-2023-48228.json",
    "cwe_ids": [
        "CWE-287"
    ]
}

References

Affected packages

Git / github.com/goauthentik/authentik

Affected ranges

Type: GIT
Repo: https://github.com/goauthentik/authentik
Events: Introduced

ed46fd629efd4307040c494faaec544a5cb7b3ee

Fixed

1516fe86dab2f62754a9c37679e0488dcf829c77

Database specific

source

"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-48228.json"