CVE-2024-23647: PKCE downgrade attack in Authentik
Summary
PKCE is a very important countermeasure in OAuth2 , both for public and confidential clients. It protects against CSRF attacks and code injection attacks. Because of this bug, an attacker can circumvent the protection PKCE offers.
Patches
authentik 2023.8.7 and 2023.10.7 fix this issue.
Details
There is a bug in our implementation of PKCE that allows an attacker to circumvent the protection that PKCE offers. PKCE adds the codechallenge’ parameter to the authorization request and adds the codeverifier’ parameter to the token request. We recently fixed a downgrade attack (in v2023.8.5 and 2023.10.4) where if the attacker removed the codeverifier’ parameter in the token request, authentik would allow the request to pass, thus circumventing PKCE’s protection. However, in the latest version of the software, another downgrade scenario is still possible: if the attacker removes the codechallenge’ parameter from the authorization request, authentik will also not do the PKCE check.
Note that this type of downgrade enables an attacker to perform a code injection attack, even if the OAuth client is using PKCE (which is supposed to protect against code injection attacks). To start the attack, the attacker must initiate the authorization process without that codechallenge’ parameter in the authorization request. But this is easy to do (just use a phishing site or email to trick the user into clicking on a link that the attacker controls – the authorization link without that codechallenge’ parameter).
The OAuth BCP (https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics) explicitly mentions this particular attack in section 2.1.1: “Authorization servers MUST mitigate PKCE Downgrade Attacks by ensuring that a token request containing a codeverifier parameter is accepted only if a codechallenge parameter was present in the authorization request, see Section 4.8.2 for details.”
For more information
If you have any questions or comments about this advisory:
- Email us at security@goauthentik.io
Other sources
Authentik is an open-source Identity Provider. There is a bug in our implementation of PKCE that allows an attacker to circumvent the protection that PKCE offers. PKCE adds the codechallenge parameter to the authorization request and adds the codeverifier parameter to the token request. Prior to 2023.8.7 and 2023.10.7, a downgrade scenario is possible: if the attacker removes the codechallenge parameter from the authorization request, authentik will not do the PKCE check. Because of this bug, an attacker can circumvent the protection PKCE offers, such as CSRF attacks and code injection attacks. Versions 2023.8.7 and 2023.10.7 fix the issue.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/goauthentik.ioto a version that resolves this vulnerability.Fixed in 2023.8.7 - Upgrade
Upgrade
go/goauthentik.ioto a version that resolves this vulnerability.Fixed in 2023.10.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2023.8.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2023.10.7
Event History
Frequently Asked Questions
What is the severity of CVE-2024-23647?
CVE-2024-23647 is considered a high severity vulnerability that affects OAuth2 implementation.
How do I fix CVE-2024-23647?
To fix CVE-2024-23647, update to Authentik version 2023.8.7 or later and ensure you are using version 2023.10.7 or later if you are on the 2023.10.x series.
What impact does CVE-2024-23647 have on my system?
CVE-2024-23647 allows attackers to bypass the PKCE countermeasure, leading to potential CSRF and code injection attacks.
Is CVE-2024-23647 a code injection vulnerability?
Yes, CVE-2024-23647 allows for code injection as part of the vulnerabilities it introduces.
Which versions of Authentik are vulnerable to CVE-2024-23647?
Versions of Authentik prior to 2023.8.7 and those within 2023.10.0 up to 2023.10.6 are vulnerable to CVE-2024-23647.