CVE-2017-2585
UnknownEPSS 2.05%
Last modified
CVE-2017-2585 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.05% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Keycloak | < 2.5.1 |
| Redhat | Single Sign On | 7.1 |
| Redhat | Single Sign On | 7.2 |
References
- http://rhn.redhat.com/errata/RHSA-2017-0876.htmlVendor Advisory
- http://www.securityfocus.com/bid/97393Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038180Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:0872Vendor Advisory
- https://access.redhat.com/errata/RHSA-2017:0873Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1412376Issue Tracking
- http://rhn.redhat.com/errata/RHSA-2017-0876.htmlVendor Advisory
- http://www.securityfocus.com/bid/97393Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038180Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:0872Vendor Advisory
- https://access.redhat.com/errata/RHSA-2017:0873Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1412376Issue Tracking
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-2585?
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.
How severe is CVE-2017-2585?
Severity scoring for CVE-2017-2585 is pending analysis. The EPSS model estimates a 2.05% probability of exploitation in the next 30 days.
How do I fix CVE-2017-2585?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-2579An out-of-bounds read vulnerability was found in netpbm befo…3.3
- CVE-2017-2580An out-of-bounds write vulnerability was found in netpbm bef…4.5
- CVE-2017-2581An out-of-bounds write vulnerability was found in netpbm bef…4.5
- CVE-2017-2582It was found that while parsing the SAML messages the StaxPa…6.5
- CVE-2017-2583The load_segment_descriptor implementation in arch/x86/kvm/e…
- CVE-2017-2584arch/x86/kvm/emulate.c in the Linux kernel through 4.9.3 all…
- CVE-2017-2586A null pointer dereference vulnerability was found in netpbm…3.3
- CVE-2017-2587A memory allocation vulnerability was found in netpbm before…3.3
- CVE-2017-2588Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-2589It was discovered that the hawtio servlet 1.4 uses a single …8.7
- CVE-2017-2590A vulnerability was found in ipa before 4.4. IdM's ca-del, c…8.1
- CVE-2017-2591389-ds-base before version 1.3.6 is vulnerable to an imprope…3.7
Are you affected by CVE-2017-2585?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST