CVE-2017-2585: org.keycloak:keycloak-core - Timing Attack Vulnerability

org.keycloak:keycloak-core Updated 02 Oct 2025

Summary

18/10/2018
Yes i
Moderate
5.9

CVE-2017-2585: keycloak-core vulnerable to timing attacks against JWS token verification. Affects org.keycloak:keycloak-core versions < 2.5.1. Fixed in 2.5.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

org.keycloak:keycloak-core is a Maven package that provides core functionality for Red Hat Keycloak, an open-source identity and access management solution. It is responsible for handling HMAC verification for JWS tokens. HMAC (Hash-based Message Authentication Code) is a cryptographic algorithm used for verifying the integrity and authenticity of a message. However, the implementation in versions prior to 2.5.1 is susceptible to a timing attack, which can potentially compromise the security of the application.

Vulnerability Detail

The vulnerability arises from the non-constant time execution of the HMAC verification method for JWS tokens in Red Hat Keycloak. A timing attack is a type of side-channel attack where an attacker can exploit variations in the execution time of a cryptographic algorithm to deduce sensitive information. In this case, an attacker could potentially determine the HMAC key used for token verification by measuring the time it takes for the verification process to complete. This could lead to unauthorized access or other security breaches.

How To Fix

Latest published version: 26.8.1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.5.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to the fixed version of the package.

Conclusion

The timing attack vulnerability in org.keycloak:keycloak-core can be mitigated by upgrading to version 2.5.1 or later. It is important to promptly apply the fix to ensure the security of the application. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.keycloak:keycloak-core →

Share this vulnerability

FAQ

org.keycloak:keycloak-core is a Maven package that provides core functionality for Red Hat Keycloak, an open-source identity and access management solution.

A timing attack is a type of side-channel attack where an attacker can exploit variations in the execution time of a cryptographic algorithm to deduce sensitive information.

HMAC verification is a process of verifying the integrity and authenticity of a message using a cryptographic algorithm called Hash-based Message Authentication Code (HMAC).

The timing attack vulnerability in org.keycloak:keycloak-core could potentially allow an attacker to determine the HMAC key used for token verification, leading to unauthorized access or other security breaches.

To fix this vulnerability, it is recommended to upgrade to version 2.5.1 or later of org.keycloak:keycloak-core.

Related vulnerabilities

Recent vulnerabilities recorded for org.keycloak:keycloak-core.

How To Fix

Latest published version: 26.8.1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.5.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback