CVE-2024-2700
highpriority · track · 0EPSS 0.003 · 21 %ileDEEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.4–7
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (25)
Products and version ranges known to be affected.
- Red Hat Integration Camel Extensions for Quarkus 1all versionscert_bundDEcpe:/a:redhat:integration:camel_extensions_for_quarkus_1
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2024-1068Red Hat Enterprise Linux (Quarkus and Netty): Mehrere SchwachstellenDeutsch2024-05-07csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift und Red Hat Enterprise Linux ausnutzen, um Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.
- GHSA-f8h5-v2vg-46rrquarkus-core leaks local environment variables from Quarkus namespace during application's build2024-04-04ghsa · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (19)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2024-2700cnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2273281cnnvd
- https://cxsecurity.com/cveshow/CVE-2024-2700/cnnvd
- https://access.redhat.com/errata/RHSA-2024:11023enisa_euvd
- https://access.redhat.com/errata/RHSA-2024:2106enisa_euvd
- https://access.redhat.com/errata/RHSA-2024:2705enisa_euvd
- https://access.redhat.com/errata/RHSA-2024:3527enisa_euvd
- https://access.redhat.com/errata/RHSA-2024:4028enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan