How severe is CVE-2024-7318?

CVE-2024-7318 has a CVSS 3.x base score of 4.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2024-7318 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-7318?

CVE-2024-7318 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-7318?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-7318 have an EU (EUVD) identifier?

Yes. CVE-2024-7318 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-3171.

When was CVE-2024-7318 published?

CVE-2024-7318 was published on 2024-09-09 and last updated on 2026-06-17.

CVE-2024-7318

CVE-2024-7318 is a medium-severity vulnerability in Redhat Build Of Keycloak with a CVSS 3.x base score of 4.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-324.

Key facts

Severity: Medium (CVSS 3.x base score 4.8)
EPSS exploit prediction: 0% (31st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-3171
Weakness: CWE-324
Affected product: Redhat Build Of Keycloak
Published: 2024-09-09
Last modified: 2026-06-17

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.

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.
How severe is CVE-2024-7318?: CVE-2024-7318 has a CVSS 3.x base score of 4.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2024-7318 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-7318?: CVE-2024-7318 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-7318?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-7318 have an EU (EUVD) identifier?: Yes. CVE-2024-7318 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-3171.
When was CVE-2024-7318 published?: CVE-2024-7318 was published on 2024-09-09 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:*

More vulnerabilities in Redhat Build Of Keycloak

CVE-2026-3047 — High (CVSS 8.8): A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is…
CVE-2026-11800 — High (CVSS 8.1): A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an…
CVE-2026-9800 — High (CVSS 8.1): A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all…
CVE-2026-7504 — High (CVSS 8.1): A flaw was found in Keycloak's URL validation logic during redirect operations. By crafting a malicious request, an…
CVE-2026-4636 — High (CVSS 8.1): A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA)…
CVE-2026-3009 — High (CVSS 8.1): A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using…

All CVEs affecting Redhat Build Of Keycloak →

Other CWE-324 vulnerabilities

CVE-2024-36031 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on…
CVE-2025-31123 — High (CVSS 8.7): Zitadel is open-source identity infrastructure software. A vulnerability existed where expired keys can be used to…
CVE-2025-2291 — High (CVSS 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-52809 — Medium (CVSS 6.8): Gogs is an open source self-hosted Git service. Prior to 0.14.3, password-reset tokens are generated using…
CVE-2024-25679 — Medium (CVSS 6.5): In PQUIC before 5bde5bb, retention of unused initial encryption keys allows attackers to disrupt a connection with a…
CVE-2025-33012 — Medium (CVSS 6.3): IBM Db2 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux…

Browse all CWE-324 vulnerabilities →