We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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.
Reserved 2024-10-28 | Published 2024-11-25 | Updated 2024-11-27 | Assigner redhat2024-10-28: | Reported to Red Hat. |
2024-11-21: | Made public. |
Red Hat would like to thank Steven Hawkins for reporting this issue.
access.redhat.com/errata/RHSA-2024:10175 (RHSA-2024:10175)
access.redhat.com/errata/RHSA-2024:10176 (RHSA-2024:10176)
access.redhat.com/errata/RHSA-2024:10177 (RHSA-2024:10177)
access.redhat.com/errata/RHSA-2024:10178 (RHSA-2024:10178)
access.redhat.com/security/cve/CVE-2024-10451
bugzilla.redhat.com/show_bug.cgi?id=2322096 (RHBZ#2322096)
Support options