CVE-2024-5203: Keycloak: login csrf
A CSRF flaw was found in Keycloak. This issue occurs due to the lack of a unique token sent during the authentication POST request, /login-actions/authenticate. An attacker could craft a malicious login page and trick a legitimate user of an application into authenticating with an attacker controlled account instead of their own.
Other sources
Rejected reason: After careful review of CVE-2024-5203, it has been determined that the issue is not exploitable in real-world scenarios. Moreover, the exploit assumes that the attacker has access to a session code parameter that matches a cookie on the Keycloak server. However the attacker does not have access to the cookie, and can therefore not craft a malicious request.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-5203?
The severity of CVE-2024-5203 is classified as medium due to its potential impact on user authentication.
How do I fix CVE-2024-5203?
To fix CVE-2024-5203, ensure that your Keycloak deployment uses the latest security patches and updates that address this CSRF vulnerability.
What software is affected by CVE-2024-5203?
CVE-2024-5203 affects the Red Hat Build of Keycloak.
Can CVE-2024-5203 allow attackers to compromise user accounts?
Yes, CVE-2024-5203 can allow attackers to compromise user accounts through a CSRF exploit.
Is there a workaround for CVE-2024-5203 until it is patched?
A potential workaround for CVE-2024-5203 involves implementing additional CSRF protections in your application until an official patch is applied.