Skip to content

ZITADEL's password reset does not respect the "Ignoring unknown usernames" setting

Moderate severity GitHub Reviewed Published Oct 10, 2023 in zitadel/zitadel • Updated Nov 5, 2023

Package

gomod github.com/zitadel/zitadel (Go)

Affected versions

< 2.37.3

Patched versions

2.37.3

Description

Impact

ZITADEL administrators can enable a setting called "Ignoring unknown usernames" which helps mitigate attacks that try to guess/enumerate usernames. While this settings was properly working during the authentication process it did not work correctly on the password reset flow. This meant that even if this feature was active that an attacker could use the password reset function to verify if an account exist within ZITADEL.

Patches

This bug has been patched in versions >2.27.2 beginning with 2.37.3 and 2.38.0

Workarounds

None available we advise to updated if this is needed.

References

None

References

@fforootd fforootd published to zitadel/zitadel Oct 10, 2023
Published by the National Vulnerability Database Oct 10, 2023
Published to the GitHub Advisory Database Oct 10, 2023
Reviewed Oct 10, 2023
Last updated Nov 5, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.074%
(34th percentile)

Weaknesses

CVE ID

CVE-2023-44399

GHSA ID

GHSA-v683-rcxx-vpff

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.