Homepage

Information Exposure Through Environmental Variables Affecting keycloak package, versions <24.0.3-r1

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (16th 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-CHAINGUARDLATEST-KEYCLOAK-6672372
  • published23 Apr 2024
  • disclosed4 Apr 2024
Report a new vulnerability Found a mistake?

Introduced: 4 Apr 2024

CVE-2024-2700  (opens in a new tab)
CWE-526  (opens in a new tab)

How to fix?

Upgrade Chainguard keycloak to version 24.0.3-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream keycloak package and not the keycloak package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application's build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been set by the developer or CI environment for testing purposes, such as dropping the database during application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application, which can lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the quarkus.* namespace. Application-specific properties are not captured.