dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2024-10451

MEDIUM · 5.9 CVSS v3.1 Published 2024-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Keycloak inadvertently captures sensitive runtime values (passwords, secrets) during the build process and embeds them as default values in the compiled bytecode. The PropertyMapper unconditionally expands environment variables, including indirect usage for SPI options and Quarkus properties, causing sensitive data to be stored as accessible defaults in all versions up to 26.0.2.

MitigationEnsure sensitive data is not present in environment variables during the Keycloak build process. Use runtime secret management mechanisms instead of embedding secrets at build time, and review all environment variable usage for SPI and Quarkus property configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Keycloak version
    Run 'keycloak --version' or check the version file in the Keycloak installation directory
    Affected if version is 26.0.2 or lower
  2. Inspect bytecode for embedded secrets
    Search compiled .class files in the Keycloak distribution for strings matching passwords, secrets, or API keys that may have been in build-time environment variables using 'strings' or grep tools
    Affected if sensitive values from environment variables appear as plaintext strings in compiled bytecode
  3. Review environment variable usage at build time
    Examine build logs, CI/CD configuration, or build scripts to identify which environment variables were set during the Keycloak build process, particularly those used for SPI options or Quarkus properties
    Affected if sensitive credentials or secrets were present in environment variables during build
  4. Check PropertyMapper configuration
    Inspect the Keycloak source or compiled classes for PropertyMapper implementation to determine if environment variable expansion is unconditionally applied to SPI and Quarkus property configurations
    Affected if PropertyMapper processes environment variables without filtering for sensitive values

A user is affected if they built Keycloak version 26.0.2 or earlier while sensitive data (passwords, secrets) existed in environment variables, as such data may now be embedded in the compiled bytecode as accessible defaults.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure sensitive data is not present in environment variables during the Keycloak build process. Use runtime secret management mechanisms instead of embedding secrets at build time, and review all environment variable usage for SPI and Quarkus property configurations.

Recommended fix Moderate confidence

Keycloak 26.0.3 or later

  1. Upgrade Keycloak to version 26.0.3 or later, which contains the fix for this vulnerability
  2. After upgrading, verify that no sensitive environment variables or credentials are inadvertently embedded in configuration by reviewing build outputs
  3. If running in a container environment, rebuild container images using the updated Keycloak version to ensure no sensitive data persists in bytecode
Caveat Review release notes for any configuration or behavioral changes between 26.0.x versions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10451 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data