Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2024-10451

Use of Hard-coded Credentials

Published: Nov 25, 2024 | Modified: Nov 25, 2024
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
5.9 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
Vulnerability-free packages from our partners
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2024-10451
CWEhttps://cwe.mitre.org/data/definitions/798.html

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.

Weakness

The product contains hard-coded credentials, such as a password or cryptographic key.

Affected Software

Name Vendor Start Version End Version
Red Hat build of Keycloak 24 RedHat rhbk/keycloak-operator-bundle:24.0.9-1 *
Red Hat build of Keycloak 24 RedHat rhbk/keycloak-rhel9:24-18 *
Red Hat build of Keycloak 24 RedHat rhbk/keycloak-rhel9-operator:24-18 *
Red Hat build of Keycloak 24.0.9 RedHat org.keycloak/keycloak-quarkus-server *
Red Hat build of Keycloak 26.0 RedHat rhbk/keycloak-operator-bundle:26.0.6-2 *
Red Hat build of Keycloak 26.0 RedHat rhbk/keycloak-rhel9:26.0-5 *
Red Hat build of Keycloak 26.0 RedHat rhbk/keycloak-rhel9-operator:26.0-6 *
Red Hat build of Keycloak 26.0.6 RedHat org.keycloak/keycloak-quarkus-server *

Extended Description

There are two main variations:

Potential Mitigations

  • For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7].
  • In Windows environments, the Encrypted File System (EFS) may provide some protection.
  • For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash.
  • Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
  • For front-end to back-end connections: Three solutions are possible, although none are complete.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use