Password confirmation via locked-account error distinction
Published Aug 22, 2022 · Updated Aug 3, 2024
Information disclosure in Keycloak before 13.0.0 allows remote attackers to confirm valid passwords after permanent account lockout. The login flow returns an account-disabled response when a locked account receives the correct password instead of the generic invalid-credentials response. Permanent brute-force lockout must be enabled and the target account locked; repeated unauthenticated login attempts can then reveal a working credential without granting a session.
Summary
What happened
Information disclosure in Keycloak before 13.0.0 allows remote attackers to confirm valid passwords after permanent account lockout. The login flow returns an account-disabled response when a locked account receives the correct password instead of the generic invalid-credentials response. Permanent brute-force lockout must be enabled and the target account locked; repeated unauthenticated login attempts can then reveal a working credential without granting a session.
The record
- CVE
- CVE-2021-3513
- Published
- Aug 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Keycloak
- Product
- Keycloak
- Classifications
- CWE-209, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 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=Fixed in keycloak v13.0.0.
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