A flaw was found in Keycloak. This flaw depends on a non-default configuration Revalidate Client Certificate to be enabled and the reverse proxy is not validating the certificate before Keycloak. Using this method an attacker may choose the certificate which will be validated by the server. If this happens and the KC_SPI_TRUSTSTORE_FILE_FILE variable is missing/misconfigured, any trustfile may be accepted with the logging information of Cannot validate client certificate trust: Truststore not available. This may not impact availability as the attacker would have no access to the server, but consumer applications Integrity or Confidentiality may be impacted considering a possible access to them. Considering the environment is correctly set to use Revalidate Client Certificate this flaw is avoidable.
Weakness
The product does not validate, or incorrectly validates, a certificate.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Build_of_quarkus | Redhat | - (including) | - (including) |
| Jboss_a-mq | Redhat | 7 (including) | 7 (including) |
| Keycloak | Redhat | - (including) | - (including) |
| Migration_toolkit_for_runtimes | Redhat | - (including) | - (including) |
| Single_sign-on | Redhat | 7.0 (including) | 7.0 (including) |
| AMQ Broker 7.11.2 | RedHat | keycloak-core | * |
| Red Hat Single Sign-On 7 | RedHat | * | |
| Red Hat Single Sign-On 7.6 for RHEL 7 | RedHat | rh-sso7-keycloak-0:18.0.8-1.redhat_00001.1.el7sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 8 | RedHat | rh-sso7-keycloak-0:18.0.8-1.redhat_00001.1.el8sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 9 | RedHat | rh-sso7-keycloak-0:18.0.8-1.redhat_00001.1.el9sso | * |
| RHEL-8 based Middleware Containers | RedHat | rh-sso-7/sso76-openshift-rhel8:7.6-24 | * |
Potential Mitigations
Related Attack Patterns
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2182196\u0026comment#0
- https://bugzilla.redhat.com/show_bug.cgi?id=2182196\u0026comment#0