Improper Certificate Validation Affecting rh-sso7-keycloak-server package, versions <0:18.0.8-1.redhat_00001.1.el7sso


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.06% (26th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RHSSO7KEYCLOAKSERVER-5293440
  • published29 Mar 2023
  • disclosed27 Mar 2023

Introduced: 27 Mar 2023

CVE-2023-1664  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade RHEL:7 rh-sso7-keycloak-server to version 0:18.0.8-1.redhat_00001.1.el7sso or higher.
This issue was patched in RHSA-2023:3883.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rh-sso7-keycloak-server package and not the rh-sso7-keycloak-server package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1