Vulnerability in Keycloak (CVE-2024-10973)
Summary
Vulnerability in Keycloak (CVE-2024-10973). Confidential information can be exposed externally. Exploitable via KC_CACHE_EMBEDDED_MTLS_ENABLED.
Original description
The description as published by the source.
A vulnerability was found in Keycloak. The environment option KC_CACHE_EMBEDDED_MTLS_ENABLED does not work and the JGroups replication configuration is always used in plain text which can allow an attacker that has access to adjacent networks related to JGroups to read sensitive information.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-10973 has been found in Keycloak.
Attackers can target a specific entry point like KC_CACHE_EMBEDDED_MTLS_ENABLED over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Keycloak CVE-2024-10973" on the vendor's site.
CVE-2024-10973 (Keycloak) — CWE-319 / CVSS v3 5.7
Attack vector: adjacent-network / no user interaction
Attack surface: KC_CACHE_EMBEDDED_MTLS_ENABLED
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-319) exists in Keycloak. Attackers reach the vulnerable code path via KC_CACHE_EMBEDDED_MTLS_ENABLED.
Check the vendor advisory for the affected versions of Keycloak. Attack surface: KC_CACHE_EMBEDDED_MTLS_ENABLED.
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Keycloak' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Keycloak' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Keycloakを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。