First published: Fri Nov 24 2023(Updated: )
An issue was found in the redirect_uri validation logic that allows for a bypass of otherwise explicitly allowed hosts. The problem arises in the verifyRedirectUri method, which attempts to enforce rules on user-controllable input, but essentially causes a desynchronization in how Keycloak and browsers interpret URLs. Keycloak, for example, receives "<a href="https://www%2ekeycloak%2eorg%2fapp%2f:y@example.com">https://www%2ekeycloak%2eorg%2fapp%2f:y@example.com</a>" and thinks the authority to be keycloak.org when it is actually example.com. This happens because the validation logic is performed on a URL decoded version, which no longer represents the original input. Refer: <a href="https://github.com/keycloak/keycloak/pull/24819">https://github.com/keycloak/keycloak/pull/24819</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Build of Keycloak |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2251407 is considered high due to the potential for unauthorized redirection.
To fix REDHAT-BUG-2251407, update your installation of Red Hat Keycloak to the latest version where the vulnerability has been addressed.
The impact of REDHAT-BUG-2251407 includes the possibility for an attacker to bypass protection mechanisms for allowed hosts.
Versions of Red Hat Keycloak that can be impacted by REDHAT-BUG-2251407 are those prior to the patched release.
Yes, REDHAT-BUG-2251407 has been publicly disclosed in Red Hat's bug tracking system.