CVE-2021-3632
Public on
Last Modified:
Description
A flaw was found in Keycloak. This vulnerability allows anyone to register a new security device or key when there is not a device already registered for any user by using the WebAuthn password-less login flow.
Additional information
- Bugzilla 1978196: keycloak: Anyone can register a new device when there is no device registered for passwordless login
- CWE-287: Improper Authentication
- FAQ: Frequently asked questions about CVE-2021-3632
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
Red Hat | NVD | |
---|---|---|
CVSS v3 Base Score | 7.5 | 7.5 |
Attack Vector | Network | Network |
Attack Complexity | High | High |
Privileges Required | None | None |
User Interaction | Required | Required |
Scope | Unchanged | Unchanged |
Confidentiality Impact | High | High |
Integrity Impact | High | High |
Availability Impact | High | High |
CVSS v3 Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Red Hat CVSS v3 Score Explanation
AC:H and UI:R, because conditions required to exploit this issue are very unlikely.
Considering an attack vector where admin account is being compromised.
Attack Complexity : High, as multiple things required to perform the attack :
- WebAuthn Passwordless login flow needs to be explicitly enabled and forced for every user.
- Attacker needs to know the username or email ID of keycloak admin.
User interaction : Required, because either admin need to cancel the registration of his security key in-between or he needs to manually delete the security key/device registered already and leave his account without any security key.
Acknowledgements
Red Hat would like to thank Florian Ritterhoff (University of Applied Sciences Munich) for reporting this issue.
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
What can I do if my product is listed as "Will not fix"?
What can I do if my product is listed as "Fix deferred"?
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.