CVE-2024-2700
Quarkus-core: leak of local configuration properties into quarkus applications
No known exploitation. EPSS puts it in the 19th percentile. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 19th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
8 events over 852 days, from the signal feeds we watch.
- Patch availableworkaround available, record updated
- Patch availableworkaround available, record updated
- Publishedweakness classified
Affected products
- HawtIO 4.0.0 for Red Hat build of Apache Camel 4DevTools & CI / ide-editor
- Red Hat AMQ Streams 2.7.0Enterprise Software / itsm-monitoring
- Red Hat build of Apicurio Registry 2.6.1 GAOSS Libraries / generic-library
- Red Hat build of Quarkus 3.2.12.FinalOSS Libraries / web-framework
- Red Hat build of Quarkus 3.8.4.redhatOSS Libraries / web-framework
- RHOSS-1.33-RHEL-8Operating Systems / linux-distro
- Red Hat build of Apache Camel 4 for Quarkus 3OSS Libraries / generic-library
- Red Hat build of Apache Camel - HawtIO 4OSS Libraries / generic-library
And 6 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Scored 7.0 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
References in the record
- access.redhat.com/errata/RHSA-2024:11023
- access.redhat.com/errata/RHSA-2024:2106
- access.redhat.com/errata/RHSA-2024:2705
And 13 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Red Hat, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI