First published: Wed May 22 2024(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Keycloak |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-5203 is classified as medium due to its potential impact on user authentication.
To fix CVE-2024-5203, ensure that your Keycloak deployment uses the latest security patches and updates that address this CSRF vulnerability.
CVE-2024-5203 affects the Red Hat Build of Keycloak.
Yes, CVE-2024-5203 can allow attackers to compromise user accounts through a CSRF exploit.
A potential workaround for CVE-2024-5203 involves implementing additional CSRF protections in your application until an official patch is applied.