# CVE-2021-3632: Keycloak allows anyone to register new security device or key for any user by using WebAuthn password-less login flow

> Attackers can register unauthorized security devices via WebAuthn when no device exists, potentially leading to account takeover in Keycloak.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qpq9-jpv4-6gwr

## What is CVE-2021-3632?

CVE-2021-3632 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-3632?

2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-core` | Maven | All versions | 15.1.0 |
| `org.keycloak:keycloak-core` | Maven | All versions | 15.1.0 |

Products: Redhat Keycloak, Redhat Single Sign-On.

## How do I fix CVE-2021-3632?

Upgrade org.keycloak:keycloak-core to 15.1.0 or later.

## Is CVE-2021-3632 being exploited?

There is no known exploitation of CVE-2021-3632 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14910](https://insights.sbomify.com/CVE-2019-14910/): Keycloak Authentication Error (critical 9.3)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3632 and fix it if it is affected.

What it is: CVE-2021-3632 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-3632 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 15.1.0
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 15.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-3632/ (Markdown: https://insights.sbomify.com/CVE-2021-3632/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-3632
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-3632
- OSV: https://osv.dev/vulnerability/CVE-2021-3632

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-3632/
Summaries are generated and may contain mistakes; the official description above is the record.