CVE-2024-7318: build of keycloak — Fix

Description

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.

Is your site exposed to CVE-2024-7318?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

4.8

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Weakness Type (CWE)

CWE-324 CWE-324

Affected Products

Vendor	Product	Versions
redhat	build_of_keycloak	22.0 — 24.0.7

References

Advisories & Patches

https://access.redhat.com/security/cve/CVE-2024-7318 https://bugzilla.redhat.com/show_bug.cgi?id=2301876

Other References

https://access.redhat.com/errata/RHSA-2024:6502 https://access.redhat.com/errata/RHSA-2024:6503

Frequently Asked Questions

What is CVE-2024-7318? +

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. It has a CVSS v3.1 base score of 4.8 (MEDIUM).

How severe is CVE-2024-7318? +

CVE-2024-7318 has a CVSS v3.1 score of 4.8 out of 10, rated MEDIUM. This is a medium-severity vulnerability that should be remediated as part of regular maintenance.

What products are affected by CVE-2024-7318? +

CVE-2024-7318 affects products from redhat, specifically: build_of_keycloak. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2024-7318? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2024-36031 9.8

In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry …

CVE-2025-31123 8.7

Zitadel is open-source identity infrastructure software. A vulnerability existed where expired keys can be used to retrieve tokens. Specifically, ZITADEL …

CVE-2025-2291 8.1

Password can be used past expiry in PgBouncer due to auth_query not taking into account Postgres its VALID UNTIL value, …

CVE-2026-39923 8.1

Flarum before 1.8.16 contains a password reset token expiry bypass vulnerability that allows unauthenticated attackers to reuse expired password reset …

CVE-2026-52809 6.8

Gogs is an open source self-hosted Git service. Prior to 0.14.3, password-reset tokens are generated using conf.Auth.ActivateCodeLives (the account-activation lifetime), …

CVE-2024-25679 6.5

In PQUIC before 5bde5bb, retention of unused initial encryption keys allows attackers to disrupt a connection with a PSK configuration …

CVE-2024-7318