Keycloak Build Process Exposes Sensitive Data
A flaw was found in Keycloak. This issue occurs because sensitive runtime values, such as passwords, may be captured during the Keycloak build process and embedded as default values in bytecode, leading to unintended information disclosure. In Keycloak 26, sensitive data specified directly in environment variables during the build process is also stored as a default values, making it accessible during runtime. Indirect usage of environment variables for SPI options and Quarkus properties is also vulnerable due to unconditional expansion by PropertyMapper logic, capturing sensitive data as default values in all Keycloak versions up to 26.0.2.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-10451US | —OT elevated | — | ||
A flaw was found in Keycloak. This issue occurs because sensitive runtime values, such as passwords, may be captured during the Keycloak build process and embedded as default value… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2024:10175WEB
- https://access.redhat.com/errata/RHSA-2024:10176WEB
- https://access.redhat.com/errata/RHSA-2024:10177WEB
- https://access.redhat.com/errata/RHSA-2024:10178WEB
- https://access.redhat.com/security/cve/CVE-2024-10451WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2322096WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/commit/198214310eb45b86707f823ccb5a2d65c814b528WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan