CVE-2023-482287.5HighCWE-287

CVE-2023-48228: OAuth2: PKCE can be fully circumvented

goauthentik · authentik

Affected: goauthentik authentik · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.3%probability of exploitation in the next 30 days

69th percentile

050100

Higher than 69% of scored CVEs

7.5HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

goauthentik · authentik< 2023.10.4; < 2023.8.5

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Authentication · Authentication
Vendor: goauthentik
Published: November 2023
Band: Possible (1 to 10%), November 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2023-48228 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.