28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
|
# CVE-2023-26481
|
||
|
|
|
||
|
|
_Reported by [@fuomag9](https://github.com/fuomag9)_
|
||
|
|
|
||
|
|
## Insufficient user check in FlowTokens by Email stage
|
||
|
|
|
||
|
|
### Summary
|
||
|
|
|
||
|
|
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.
|
||
|
|
|
||
|
|
### Patches
|
||
|
|
|
||
|
|
authentik 2022.12.3, 2023.1.3, 2023.2.3 fix this issue.
|
||
|
|
|
||
|
|
### Impact
|
||
|
|
|
||
|
|
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.
|
||
|
|
|
||
|
|
### Workaround
|
||
|
|
|
||
|
|
It is recommended to upgrade to the patched version of authentik. Regardless, for custom recovery flows it is recommended to add a policy that checks if the flow is restored, and skips the identification stage.
|
||
|
|
|
||
|
|
### For more information
|
||
|
|
|
||
|
|
If you have any questions or comments about this advisory:
|
||
|
|
|
||
|
|
- Email us at [security@goauthentik.io](mailto:security@goauthentik.io)
|