GitHub Advisoryadvisory · Maven

GHSA-f8h5-v2vg-46rr quarkus-core leaks local environment variables from Quarkus namespace during application's build

HIGH Published 2024-04-04 Modified 2024-12-13 Official page ↗
Aliases
CVE-2024-2700
Ecosystem
Maven
Packages
io.quarkus:quarkus-core
Severity
High
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-526
Reviewed
2024-04-04

Affected packages

• Maven io.quarkus:quarkus-core: >= 3.9.0.CR1, < 3.9.2 → fixed in 3.9.2 • Maven io.quarkus:quarkus-core: >= 3.3.0.CR1, < 3.8.4 → fixed in 3.8.4 • Maven io.quarkus:quarkus-core: < 3.2.12.Final → fixed in 3.2.12.Final

Description

A vulnerability was found in the quarkus-core component. Quarkus captures the local environment variables from the Quarkus namespace during the application's build. Thus, running the resulting application inherits the values captured at build time. However, some local environment variables may have been set by the developer / CI environment for testing purposes, such as dropping the database during the 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. It may lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the `quarkus.*` namespace. So, application-specific properties are not captured.

Related

Alias · CVE (1)

  • CVE-2024-2700 A vulnerability was found in the quarkus-core component. vulnerability

Weakness · CWE (1)

  • CWE-526 Cleartext Storage of Sensitive Information in an Environment Variable weakness

References