CVE-2023-39522 – @goauthentik/api

Package

Manager: npm
Name: @goauthentik/api
Vulnerable Version: >=2023.6.0 <2023.6.2 || >=0 <2023.5.6

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00373 pctl0.58206

Details

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-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](mailto:security@goauthentik.io)

Metadata

Created: 2023-08-29T23:34:51Z
Modified: 2023-08-29T23:34:51Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/08/GHSA-vmf9-6pcv-xr87/GHSA-vmf9-6pcv-xr87.json
CWE IDs: ["CWE-203"]
Alternative ID: GHSA-vmf9-6pcv-xr87
Finding: F026
Auto approve: 1