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
                    | Link | Resource | 
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=1412376 | Issue Tracking | 
| https://access.redhat.com/errata/RHSA-2017:0873 | Vendor Advisory | 
| https://access.redhat.com/errata/RHSA-2017:0872 | Vendor Advisory | 
| http://www.securitytracker.com/id/1038180 | Third Party Advisory VDB Entry | 
| http://www.securityfocus.com/bid/97393 | Third Party Advisory VDB Entry | 
| http://rhn.redhat.com/errata/RHSA-2017-0876.html | Vendor Advisory | 
Configurations
                    Configuration 1 (hide)
                                
                                
  | 
                        
Configuration 2 (hide)
| AND | 
                                
                                
 
  | 
                        
Information
                Published : 2018-03-12 08:29
Updated : 2018-04-12 08:14
NVD link : CVE-2017-2585
Mitre link : CVE-2017-2585
JSON object : View
CWE
                
                    
                        
                        CWE-200
                        
            Exposure of Sensitive Information to an Unauthorized Actor
Products Affected
                redhat
- enterprise_linux_server
 - keycloak
 - single_sign_on
 


