Use of a Key Past its Expiration Date Affecting keycloak-config-cli package, versions <6.4.0-r1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.26% (50th percentile)

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-CHAINGUARDLATEST-KEYCLOAKCONFIGCLI-9021640
  • published2 Mar 2025
  • disclosed9 Sept 2024

Introduced: 9 Sep 2024

CVE-2024-7318  (opens in a new tab)
CWE-324  (opens in a new tab)

How to fix?

Upgrade Chainguard keycloak-config-cli to version 6.4.0-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream keycloak-config-cli package and not the keycloak-config-cli package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

A vulnerability was found in Keycloak. Expired OTP codes are still usable when using FreeOTP when the OTP token period is set to 30 seconds (default). Instead of expiring and deemed unusable around 30 seconds in, the tokens are valid for an additional 30 seconds totaling 1 minute. A one time passcode that is valid longer than its expiration time increases the attack window for malicious actors to abuse the system and compromise accounts. Additionally, it increases the attack surface because at any given time, two OTPs are valid.

CVSS Base Scores

version 3.1