CVE-2023-39522
published 2023-08-29CVE-2023-39522: goauthentik is an open-source Identity Provider. In affected versions using a recovery flow with an identification stage an attacker is able to determine if a…
PriorityP428medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
0.51%
39.8th percentile
goauthentik is an open-source Identity Provider. In affected versions 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. This issue has been addressed in versions 2023.5.6 and 2023.6.2. Users are advised to upgrade. There are no known workarounds for this issue.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| goauthentik | api | >= 0 < 2023.5.6 | 2023.5.6 |
| goauthentik | api | >= 2023.6.0 < 2023.6.2 | 2023.6.2 |
| goauthentik | authentik | < 2023.5.6 | 2023.5.6 |
| goauthentik | authentik | — | — |
| goauthentik | authentik | >= 2023.6.0 < 2023.6.2 | 2023.6.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Username enumeration attack in goauthentik
osv·2023-08-29
CVE-2023-39522 [MEDIUM] Username enumeration attack in goauthentik
Username enumeration attack in goauthentik
## Summary
Using a recovery flow with an identification stage an attacker is able to determine if a username exists.
## Impact
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.
## Details
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-pract
GHSA
Username enumeration attack in goauthentik
ghsa·2023-08-29
CVE-2023-39522 [MEDIUM] CWE-203 Username enumeration attack in goauthentik
Username enumeration attack in goauthentik
## Summary
Using a recovery flow with an identification stage an attacker is able to determine if a username exists.
## Impact
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.
## Details
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-pract
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/goauthentik/authentik/commit/aa874dd92a770d5f8cd8f265b7cdd31cd73a4599https://github.com/goauthentik/authentik/security/advisories/GHSA-vmf9-6pcv-xr87https://github.com/goauthentik/authentik/commit/aa874dd92a770d5f8cd8f265b7cdd31cd73a4599https://github.com/goauthentik/authentik/security/advisories/GHSA-vmf9-6pcv-xr87
2023-08-29
Published