First published: Wed Jan 11 2017(Updated: )
Keycloak implented HMAC verification using a comparison method that does not operate in constant time. This potentially leaves the application open to timing attacks.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.keycloak:keycloak-core | <2.5.1 | 2.5.1 |
redhat/keycloak | <2.5.1 | 2.5.1 |
Red Hat Keycloak | <2.5.1 | |
Red Hat Single Sign-On | =7.1 | |
Red Hat Single Sign-On | =7.2 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux server | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-2585 is considered a high severity vulnerability due to the potential for timing attacks.
To fix CVE-2017-2585, you should upgrade Red Hat Keycloak to version 2.5.1 or later.
CVE-2017-2585 affects applications using Red Hat Keycloak versions prior to 2.5.1 and could lead to security vulnerabilities.
CVE-2017-2585 can potentially facilitate timing attacks that exploit the non-constant time implementation of HMAC verification.
There is no documented workaround for CVE-2017-2585; upgrading to a secure version is the recommended action.