quarkus-core leaks local environment variables from Quarkus namespace during application's build
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-2700US | — | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2024:11023WEB
- https://access.redhat.com/errata/RHSA-2024:2106WEB
- https://access.redhat.com/errata/RHSA-2024:2705WEB
- https://access.redhat.com/errata/RHSA-2024:3527WEB
- https://access.redhat.com/errata/RHSA-2024:4028WEB
- https://access.redhat.com/errata/RHSA-2024:4873WEB
- https://access.redhat.com/security/cve/CVE-2024-2700WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2273281WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan