CVE-2024-7260: Keycloak-core: open redirect on account page

Published Jul 31, 2024
·
Updated

A vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referreruri parameters are made to trick a user to visit a malicious webpage; this vulnerability is called an Open Redirect.

A trusted URL can fool both users and automation into believing that the URL is safe when in fact it redirects to a malicious server. This can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks.

Once a crafted URL is made, it can be sent to a Keycloak admin via email for example, and it will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can target users whom they know are Keycloak admins for further attacks in this way. It may be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. Finally, the malicious actor can further obfuscate the redirecturi using URL encoding, to hide the text of the actual malicious website domain.

Other sources

An open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referreruri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks.

Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirecturi using URL encoding, to hide the text of the actual malicious website domain.

GitHub

An open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referreruri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks. Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirecturi using URL encoding, to hide the text of the actual malicious website domain.

NVD

Affected Software

3 affected componentsFixes available
maven/org.keycloak:keycloak-core<24.0.7
24.0.7
redhat Build Of Keycloak<24.0.7
redhat keycloak<24.0.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.keycloak:keycloak-core to a version that resolves this vulnerability.

    Fixed in 24.0.7

Event History

Jul 31, 2024
Data Sourced
via Red Hat·03:05 AM
DescriptionSeverityAffected Software
Sep 9, 2024
CVE Published
via MITRE·06:49 PM
Data Sourced
via MITRE·06:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:31 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-7260?

The severity of CVE-2024-7260 is considered moderately high due to its potential to facilitate phishing attacks.

2

How do I fix CVE-2024-7260?

To fix CVE-2024-7260, upgrade Keycloak to version 24.0.7 or later, which contains the necessary patches.

3

What are the potential impacts of CVE-2024-7260?

CVE-2024-7260 can allow attackers to redirect users to malicious websites, leading to possible information disclosure or phishing scams.

4

Which software versions are affected by CVE-2024-7260?

CVE-2024-7260 affects Keycloak versions prior to 24.0.7, including the Red Hat Build of Keycloak.

5

How can I identify if my system is vulnerable to CVE-2024-7260?

You can identify if your system is vulnerable by checking the installed Keycloak version against the affected versions outlined in CVE-2024-7260.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203