cve.bz

CVE-2023-1664 redhat: Improper Certificate Validation

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in redhat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.keycloak:keycloak-core 21.1.2.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-01-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-1664 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-1664?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-1664?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-1664 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:jboss_a-mq7
redhat:single_sign-on7.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5cc8-pgp5-7mpmMavenorg.keycloak:keycloak-core<21.1.221.1.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatred_hat_single_sign_on:7.6::el7rh-sso7-keycloak, rh-sso7-keycloak-server0:18.0.8-1.redhat_00001.1.el7ssoRHSA-2023:3883
Red Hatred_hat_single_sign_on:7.6::el8rh-sso7-keycloak, rh-sso7-keycloak-server0:18.0.8-1.redhat_00001.1.el8ssoRHSA-2023:3884
Red Hatred_hat_single_sign_on:7.6::el9rh-sso7-keycloak, rh-sso7-keycloak-server0:18.0.8-1.redhat_00001.1.el9ssoRHSA-2023:3885

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Impact rated as a low impact considering there's a mitigation for this issue which would be consider the environment is correctly set with the truststore file. With these settings, the environment there's no evidence of attack possibility. Also it's possible to track under the server logs for more evidences.

Red Hat's mitigation

Make sure KC_SPI_TRUSTSTORE_FILE_FILE is correctly set and the logs are not reporting the "Cannot validate client certificate trust: Truststore not available" after an attempt to explore the vulnerability. Note this message may happen under other scenarios and reasons but the expected behavior would be that a non-valid certificate to pass.

ProductPackageStateAdvisory
AMQ Broker 7.11.2keycloak-coreFixed 2023-10-05RHSA-2023:5491
Red Hat Single Sign-On 7rh-sso7-keycloakFixed 2023-06-27RHSA-2023:3892
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.8-1.redhat_00001.1.el7ssoFixed 2023-06-27RHSA-2023:3883
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.8-1.redhat_00001.1.el8ssoFixed 2023-06-27RHSA-2023:3884
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.8-1.redhat_00001.1.el9ssoFixed 2023-06-27RHSA-2023:3885
RHEL-8 based Middleware Containersrh-sso-7/sso76-openshift-rhel8:7.6-24Fixed 2023-06-27RHSA-2023:3888
Migration Toolkit for Runtimesorg.keycloak-keycloak-coreAffected
Red Hat build of Apicurio Registry 2keycloak-coreFix deferred
Red Hat build of Quarkuskeycloak-coreFix deferred
Red Hat Fuse 7keycloak-coreFix deferred
Red Hat Satellite 6keycloak-httpd-client-installNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-1664.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON