It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the users session. This could lead to information disclosure, or permit further possible attacks.
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Keycloak | Redhat | * | 2.3.0 (excluding) |
| Red Hat Single Sign-On 7.0 | RedHat | * |
Such a scenario is commonly observed when: