Keycloak denial of service via default roles in client registration
Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.8 · Red Hat Single Sign-On 7
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat build of Keycloak 26.6 | — |
|
| Red Hat Red Hat build of Keycloak 26.6 | — |
|
| Red Hat Red Hat build of Keycloak 26.6 | — |
|
| Red Hat Red Hat build of Keycloak 26.6.8 | — | No fix yet |
| Red Hat Red Hat build of Keycloak 26.6.8 | — | No fix yet |
| Red Hat Red Hat Single Sign-On 7 | — | No fix yet |
Original description
A flaw was found in Keycloak. The Dynamic Client Registration (DCR) endpoint does not properly validate authorization when processing the deprecated defaultRoles field. An authenticated attacker with client creation privileges or an Initial Access Token (IAT) can inject excessive roles into the realm's default roles configuration. This causes clients across the realm to generate bloated access tokens, resulting in performance and memory degradation that can lead to a Denial of Service (DoS).
From the CVE record · redhat