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 user's 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.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8609 | vendor advisory issue tracking |
http://rhn.redhat.com/errata/RHSA-2016-2945.html | vendor advisory |
http://www.securitytracker.com/id/1037460 | third party advisory vdb entry |
http://www.securityfocus.com/bid/95070 | third party advisory vdb entry |