High [CVE-2024-2700] Quarkus-core: leak of local configuration properties into quarkus applications
This high-severity Red Hat Linux advisory covers CVE-2024-2700 affecting Red Hat build of Quarkus 3.2.12.Final, Red Hat build of Quarkus 3.8.4.redhat, RHOSS-1.33-RHEL-8.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
Affected products named by the advisory: Red Hat build of Quarkus 3.2.12.Final; Red Hat build of Quarkus 3.8.4.redhat; RHOSS-1.33-RHEL-8; Red Hat build of Apache Camel 4 for Quarkus 3; and 6 more.
Affected products named by the advisory: Red Hat build of Apache Camel - HawtIO 4; Red Hat Build of Keycloak; Red Hat build of OptaPlanner 8; Red Hat Integration Camel K 1; and 1 more.
- 3.8.4
- 3.2.12
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.