| Package | Affected versions | Patched versions |
|---|---|---|
| authentik | ≥ 2023.6.0, < 2023.6.2< 2023.5.6 | 2023.6.22023.5.6 |
| @goauthentik/api | ≥ 2023.6.0, < 2023.6.2< 2023.5.6 | 2023.6.22023.5.6 |
This advisory has been withdrawn due to an incorrect package mapping error. This link is maintained to preserve external references.
Using a recovery flow with an identification stage an attacker is able to determine if a username exists.
Only setups configured with a recovery flow are impacted by this. Anyone with a user account on a system with the recovery flow described above is susceptible to having their username/email revealed as existing.
An attacker can easily enumerate and check users' existence using the recovery flow, as a clear message is shown when a user doesn't exist. Depending on configuration this can either be done by username, email, or both.
The invalid and valid usernames should both show the same message and always send an email. Article for reference here: https://postmarkapp.com/guides/password-reset-email-best-practices#how-to-make-sure-your-password-reset-emails-are-secure
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free