CVE-2021-3513 Incorrect implementation of lockout feature in Keycloak
Keycloak displays incorrect error messages during failed logins, enabling brute force attacks even when permanent lockout is enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-3513?
CVE-2021-3513 is a high-severity vulnerability in Redhat Keycloak, published on 22 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A flaw was found in keycloak where a brute force attack is possible even when the permanent lockout feature is enabled. This is due to a wrong error message displayed when wrong credentials are entered. The highest threat from this vulnerability is to confidentiality.
Which versions are affected by CVE-2021-3513?
2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.keycloak:keycloak-parent Maven | All versions | 13.0.0 |
org.keycloak:keycloak-parent Maven | All versions | 13.0.0 |
Products include Redhat Keycloak.
How do I fix CVE-2021-3513?
Upgrade org.keycloak:keycloak-parent to 13.0.0 or later.
Is CVE-2021-3513 being exploited?
There is no known exploitation of CVE-2021-3513 in the wild and no public exploit code.
Other vulnerabilities in Redhat Keycloak
- CVE-2022-4361 Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC
- CVE-2022-1245 Keycloak vulnerable to privilege escalation on Token Exchange feature
- CVE-2021-20195 keycloak Self Stored Cross-site Scripting vulnerability
- CVE-2019-14910 Keycloak Authentication Error
- CVE-2019-14909 Keycloak Authentication Error
Sources
Also known as GHSA-xv7h-95r7-595j.