Account recovery denial via username-email collision
Published Aug 26, 2022 · Updated Aug 3, 2024
Improper input validation in Red Hat build of Keycloak before 24.0.1 allows remote attackers to block account recovery via registration. When email login is enabled, username validation checks usernames before email uniqueness and accepts a username equal to an existing user's email. Self-registration must also be enabled; the collision blocks the existing user's sign-in or password recovery but does not grant access to that account.
Summary
What happened
Improper input validation in Red Hat build of Keycloak before 24.0.1 allows remote attackers to block account recovery via registration. When email login is enabled, username validation checks usernames before email uniqueness and accepts a username equal to an existing user's email. Self-registration must also be enabled; the collision blocks the existing user's sign-in or password recovery but does not grant access to that account.
The record
- CVE
- CVE-2021-3754
- Published
- Aug 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-20, CWE-670, T1531
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Not-Known
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo