CVE-2023-48228

Description

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.

Weakness classification

• security-advisories@github.com: CWE-287

Primary references

• security-advisories@github.com — Product
• security-advisories@github.com — Patch
• security-advisories@github.com — Patch
• security-advisories@github.com — Patch
• security-advisories@github.com — Patch
• security-advisories@github.com — Patch
• security-advisories@github.com — Patch
• security-advisories@github.com — Release Notes
• security-advisories@github.com — Release Notes
• security-advisories@github.com — Exploit, Vendor Advisory
• af854a3a-2127-422b-91ae-364da2661108 — Product
• af854a3a-2127-422b-91ae-364da2661108 — Patch