First published: Fri Apr 28 2023(Updated: )
A flaw was found in Keycloak. A Keycloak server configured to support mTLS authentication for OAuth/OpenID clients does not properly verify the client certificate chain. A client that possesses a proper certificate can authorize itself as any other client, therefore, access data that belongs to other clients.
Credit: secalert@redhat.com secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.keycloak:keycloak-services | <21.1.2 | 21.1.2 |
Redhat Keycloak | ||
Redhat Openshift Container Platform | =4.9 | |
Redhat Openshift Container Platform | =4.10 | |
Redhat Openshift Container Platform | =4.11 | |
Redhat Openshift Container Platform | =4.12 | |
Redhat Single Sign-on | =7.6 | |
Redhat Enterprise Linux | =7.0 | |
Redhat Enterprise Linux | =8.0 | |
Redhat Enterprise Linux | =9.0 | |
redhat/keycloak | <18.0 | 18.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-2422 is a vulnerability in Keycloak that allows a client with a proper certificate to authorize itself as any other client and access data belonging to other clients.
CVE-2023-2422 has a severity rating of 7.1 (high).
CVE-2023-2422 affects Keycloak versions up to and excluding 21.1.2, as well as Redhat Keycloak versions up to and excluding 18.0.
To fix CVE-2023-2422, update your Keycloak server to version 21.1.2 or later, or update your Redhat Keycloak version to 18.0 or later.
You can find more information about CVE-2023-2422 on the Keycloak security advisories page and the NVD website.