Description
Keycloak provides a mechanism called Client Policies to enforce security requirements on clients, such as requiring them to use signed JWTs for authentication. A flaw was discovered where this enforcement can be bypassed. An attacker with valid client credentials can provide a fake, unsigned assertion header that tricks the system into thinking the policy requirements have been met. This allows the attacker to authenticate using simpler methods like a client secret even when the administrator has mandated more secure, signed assertions.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6.7-3 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-20 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-20 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6.7
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.6.7
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.6.7
Default version status: unaffected
Red Hat Red Hat Data Grid 8
Default version status: affected
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
Default version status: affected
Red Hat Red Hat Single Sign-On 7
Default version status: affected