GHSA-vmf9-6pcv-xr87
Suggest an improvement- Source
- https://github.com/advisories/GHSA-vmf9-6pcv-xr87
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/08/GHSA-vmf9-6pcv-xr87/GHSA-vmf9-6pcv-xr87.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-vmf9-6pcv-xr87
- Aliases
- Related
- Published
- 2023-08-29T23:34:51Z
- Modified
- 2023-11-08T04:13:14.214713Z
- Severity
-
- 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CVSS Calculator
- Summary
- Username enumeration attack in goauthentik
- Details
-
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-practices#how-to-make-sure-your-password-reset-emails-are-secure
For more information
If you have any questions or comments about this advisory:
- Email us at security@goauthentik.io
- Database specific
{ "nvd_published_at": "2023-08-29T18:15:08Z", "github_reviewed_at": "2023-08-29T23:34:51Z", "github_reviewed": true, "severity": "MODERATE", "cwe_ids": [ "CWE-203" ] }- References
Affected packages
npm / @goauthentik/api
Package
- Name
- @goauthentik/api
- View open source insights on deps.dev
- Purl
- pkg:npm/%40goauthentik/api
npm / @goauthentik/api
Package
- Name
- @goauthentik/api
- View open source insights on deps.dev
- Purl
- pkg:npm/%40goauthentik/api