CVE-2023-26481
Assigner: GitHub_M
Published: 2023-03-04T00:30:16.509Z
State: PUBLISHED
title: Insufficient user check in FlowTokens by Email stage
problemTypes: descriptions: cweId: CWE-345
description: CWE-345: Insufficient Verification of Data Authenticity
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 9.1
baseSeverity: CRITICAL
confidentialityImpact: HIGH
integrityImpact: HIGH
privilegesRequired: HIGH
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
version: 3.1
affected: vendor: goauthentik
product: authentik
versions: version: < 2023.2.3
status: affected
version: < 2023.1.3
status: affected
version: < 2022.12.2
status: affected
descriptions: value: authentik is an open-source Identity Provider. Due to an insufficient access check, a recovery flow link that is created by an admin (or sent via email by an admin) can be used to set the password for any arbitrary user. This attack is only possible if a recovery flow exists, which has both an Identification and an Email stage bound to it. If the flow has policies on the identification stage to skip it when the flow is restored (by checking `request.context['is_restored']`), the flow is not affected by this. With this flow in place, an administrator must create a recovery Link or send a recovery URL to the attacker, who can, due to the improper validation of the token create, set the password for any account. Regardless, for custom recovery flows it is recommended to add a policy that checks if the flow is restored, and skips the identification stage. This issue has been fixed in versions 2023.2.3, 2023.1.3 and 2022.12.2.

source: advisory: GHSA-3xf5-pqvf-rqq3
discovery: UNKNOWN