Use of Hard-coded Credentials Affecting org.keycloak/keycloak-quarkus-server package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-ORGKEYCLOAKKEYCLOAKQUARKUSSERVER-8444385
  • published29 Nov 2024
  • disclosed21 Nov 2024

Introduced: 21 Nov 2024

CVE-2024-10451  (opens in a new tab)
CWE-798  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 org.keycloak/keycloak-quarkus-server.

NVD Description

Note: Versions mentioned in the description apply only to the upstream org.keycloak/keycloak-quarkus-server package and not the org.keycloak/keycloak-quarkus-server package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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.

CVSS Scores

version 3.1