CVE-2024-10973: Keycloak: cli option for encrypted jgroups ignored
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.
Security readout for executives and security teams
Plain-English summary
Keycloak may send cluster replication traffic in plaintext even when an environment option is intended to enable embedded mTLS. An attacker with access to adjacent JGroups-related networks could read sensitive information. This is not an internet-wide remote code execution issue, but it matters for clustered deployments and network segmentation.
Executive priority
Prioritize review for production clustered Keycloak environments, especially where cluster networks are shared or weakly segmented. Business risk is confidentiality exposure of identity platform data, not full system takeover based on current sources.
Technical view
CVE-2024-10973 is a CWE-319 cleartext transmission issue in Keycloak. The `KC_CACHE_EMBEDDED_MTLS_ENABLED` option reportedly does not work, so JGroups replication configuration is always plaintext. CVSS is 5.7 Medium: adjacent attack vector, low complexity, low privileges, no user interaction, high confidentiality impact.
Likely exposure
Most relevant to clustered Keycloak deployments using embedded cache/JGroups where adjacent network access to replication traffic is possible. The source lists Keycloak 22.0, 24.0, and 26.0.6 as affected, while listed Red Hat products are marked unaffected.
Exploitation context
No CISA KEV listing or provided source states active exploitation. Successful exploitation requires access to adjacent networks related to JGroups traffic and appears limited to reading exposed sensitive information, not modifying data or causing denial of service.
Researcher notes
The public record identifies the broken mTLS environment option and plaintext JGroups behavior, but does not provide patch details in the supplied bundle. Treat remediation status as incomplete and follow vendor advisories rather than assuming a configuration-only fix.
Mitigation direction
Check Red Hat and upstream Keycloak guidance for fixed versions or configuration direction.
Do not rely on `KC_CACHE_EMBEDDED_MTLS_ENABLED` to encrypt JGroups traffic until verified.
Restrict JGroups-related network access to trusted cluster nodes only.
Assess whether affected Keycloak versions are deployed in clustered mode.
Validation and detection
Inventory Keycloak versions and identify clustered deployments using embedded cache or JGroups.
Review network paths to confirm who can reach JGroups replication traffic.
Verify whether Red Hat Build of Keycloak or EAP packages are in use and marked unaffected.
Track Red Hat Bugzilla and CVE pages for remediation updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-319: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-319 · source CWE mapping
Cleartext Transmission of Sensitive Information
Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.