Covert Timing Channel Affecting keycloak package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL10-KEYCLOAK-9846033
- published28 Apr 2025
- disclosed4 Apr 2017
Introduced: 4 Apr 2017
CVE-2017-2585 (opens in a new tab)How to fix?
There is no fixed version for RHEL:10 keycloak.
NVD Description
Note: Versions mentioned in the description apply only to the upstream keycloak package and not the keycloak package as distributed by RHEL.
See How to fix? for RHEL:10 relevant fixed versions and status.
Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1412376
- https://access.redhat.com/security/cve/CVE-2017-2585
- http://rhn.redhat.com/errata/RHSA-2017-0876.html
- http://www.securityfocus.com/bid/97393
- http://www.securitytracker.com/id/1038180
- https://access.redhat.com/errata/RHSA-2017:0872
- https://access.redhat.com/errata/RHSA-2017:0873