CVE-2017-2585

low-risk
Published 2018-03-12

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.

Do I need to act?

-
0.67% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.9/10 Medium
NETWORK / HIGH complexity

Affected Products (3)

Single Sign On
Single Sign On

Affected Vendors

Redhat

References (12)

Vendor Advisory http://rhn.redhat.com/errata/RHSA-2017-0876.html
Third Party Advisory http://www.securityfocus.com/bid/97393
Third Party Advisory http://www.securitytracker.com/id/1038180
Vendor Advisory https://access.redhat.com/errata/RHSA-2017:0872
Vendor Advisory https://access.redhat.com/errata/RHSA-2017:0873
Issue Tracking https://bugzilla.redhat.com/show_bug.cgi?id=1412376
Vendor Advisory http://rhn.redhat.com/errata/RHSA-2017-0876.html
Third Party Advisory http://www.securityfocus.com/bid/97393
Third Party Advisory http://www.securitytracker.com/id/1038180
Vendor Advisory https://access.redhat.com/errata/RHSA-2017:0872
Vendor Advisory https://access.redhat.com/errata/RHSA-2017:0873
Issue Tracking https://bugzilla.redhat.com/show_bug.cgi?id=1412376
29
/ 100
low-risk
Severity 18/34 · Moderate
Exploitability 2/34 · Minimal
Exposure 9/34 · Low