Fedora Account System
Red Hat Associate
Red Hat Customer
The OpenID Connect logout endpoint (GET /realms/{realm}/protocol/openid-connect/logout) still applies a client's post-logout redirect URI configuration after the client has been disabled. A disabled client should be rejected with an error, as the authorization endpoint does, and its redirect allowlist should be ignored. Instead, if a disabled client was configured with a permissive post-logout redirect URI (for example "*", or a redirect URI of "*" with an empty post-logout redirect URI), a request for the logout endpoint with that client_id and an arbitrary post_logout_redirect_uri redirects the browser to the attacker-chosen URL. When the victim has an active session, Keycloak shows the logout confirmation page first. When the victim has no active session, the browser is redirected directly, which results in an open redirect. Disabling a misconfigured client is expected to neutralize the issue, and it does not. The same behavior was confirmed on a build of main, where the redirect is also honored after the user confirms the logout.