CVE-2017-2585: Infoleak
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
| 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 | |
| Red Hat Enterprise Linux Server | =6.0 | |
| Red Hat Enterprise Linux Server | =7.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2017-2585
- https://access.redhat.com/errata/RHSA-2017:0872
- https://access.redhat.com/errata/RHSA-2017:0873
- https://bugzilla.redhat.com/show_bug.cgi?id=1412376
- https://github.com/advisories/GHSA-w6gv-3r3v-gwgj (Advisory)
- http://rhn.redhat.com/errata/RHSA-2017-0876.html
- https://web.archive.org/web/20170420113802/http://www.securitytracker.com/id/1038180
- https://web.archive.org/web/20200227175650/http://www.securityfocus.com/bid/97393
- http://www.securityfocus.com/bid/97393
- http://www.securitytracker.com/id/1038180
- https://access.redhat.com/errata/RHSA-2017:0876
Frequently Asked Questions
What is the severity of CVE-2017-2585?
CVE-2017-2585 is considered a high severity vulnerability due to the potential for timing attacks.
How do I fix CVE-2017-2585?
To fix CVE-2017-2585, you should upgrade Red Hat Keycloak to version 2.5.1 or later.
What types of applications are affected by CVE-2017-2585?
CVE-2017-2585 affects applications using Red Hat Keycloak versions prior to 2.5.1 and could lead to security vulnerabilities.
What kind of attacks can CVE-2017-2585 facilitate?
CVE-2017-2585 can potentially facilitate timing attacks that exploit the non-constant time implementation of HMAC verification.
Is there a workaround for CVE-2017-2585?
There is no documented workaround for CVE-2017-2585; upgrading to a secure version is the recommended action.
- collector/github-advisory-latest
- alias/GHSA-w6gv-3r3v-gwgj
- alias/CVE-2017-2585
- collector/github-advisory
- agent/first-publish-date
- agent/type
- collector/redhat-bugzilla
- source/Red Hat
- agent/software-canonical-lookup
- agent/references
- agent/weakness
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/author
- agent/softwarecombine
- agent/tags
- collector/nvd-cve
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/maven
- package-manager/redhat
- vendor/redhat
- canonical/red hat keycloak
- canonical/red hat single sign-on
- version/red hat single sign-on/7.1
- version/red hat single sign-on/7.2
- canonical/red hat enterprise linux server
- version/red hat enterprise linux server/6.0
- version/red hat enterprise linux server/7.0