Bug 1953439 (CVE-2021-3513) - CVE-2021-3513 keycloak: Brute force attack is possible even after the account lockout
Summary: CVE-2021-3513 keycloak: Brute force attack is possible even after the account...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2021-3513
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1953432 1953561
TreeView+ depends on / blocked
 
Reported: 2021-04-26 06:33 UTC by Paramvir jindal
Modified: 2022-11-29 12:48 UTC (History)
7 users (show)

Fixed In Version: keycloak 13.0.0
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2021-09-14 18:21:15 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:3527 0 None None None 2021-09-14 12:34:33 UTC
Red Hat Product Errata RHSA-2021:3528 0 None None None 2021-09-14 12:31:23 UTC
Red Hat Product Errata RHSA-2021:3529 0 None None None 2021-09-14 12:32:26 UTC
Red Hat Product Errata RHSA-2021:3534 0 None None None 2021-09-14 12:37:47 UTC

Description Paramvir jindal 2021-04-26 06:33:02 UTC 
Even though Permanent Lockout is a feature of Brute Force Detection, it doesn't protect the account from exposing his/hers credentials.
Once the account is locked, the malicious actor can keep trying to login and will get informed the account is disabled once the password is correct.

https://issues.redhat.com/browse/KEYCLOAK-17835
Comment 2 Paramvir jindal 2021-05-11 07:01:32 UTC 
Acknowledgments:

Name: Michał Knapik & Peter Nicholson (u2i)
Comment 5 errata-xmlrpc 2021-09-14 12:31:21 UTC 
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.4 for RHEL 7

Via RHSA-2021:3528 https://access.redhat.com/errata/RHSA-2021:3528
Comment 6 errata-xmlrpc 2021-09-14 12:32:25 UTC 
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.4 for RHEL 8

Via RHSA-2021:3529 https://access.redhat.com/errata/RHSA-2021:3529
Comment 7 errata-xmlrpc 2021-09-14 12:34:32 UTC 
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.4 for RHEL 6

Via RHSA-2021:3527 https://access.redhat.com/errata/RHSA-2021:3527
Comment 8 errata-xmlrpc 2021-09-14 12:37:46 UTC 
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.4.9

Via RHSA-2021:3534 https://access.redhat.com/errata/RHSA-2021:3534
Comment 9 Product Security DevOps Team 2021-09-14 18:21:15 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-3513
Note You need to log in before you can comment on or make changes to this bug.