Summary
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.
Impact
CVE-2024-2700 has a CVSS score of 7.0 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.9.2, 3.8.4, 3.2.12.Final); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
io.quarkus:quarkus-core to 3.9.2 or later; io.quarkus:quarkus-core to 3.8.4 or later; io.quarkus:quarkus-core to 3.2.12.Final or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-2700? CVE-2024-2700 is a high-severity security vulnerability in io.quarkus:quarkus-core (maven), affecting versions >= 3.9.0.CR1, <= 3.9.1. It is fixed in 3.9.2, 3.8.4, 3.2.12.Final.
- How severe is CVE-2024-2700? CVE-2024-2700 has a CVSS score of 7.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of io.quarkus:quarkus-core are affected by CVE-2024-2700? io.quarkus:quarkus-core (maven) versions >= 3.9.0.CR1, <= 3.9.1 is affected.
- Is there a fix for CVE-2024-2700? Yes. CVE-2024-2700 is fixed in 3.9.2, 3.8.4, 3.2.12.Final. Upgrade to this version or later.
- Is CVE-2024-2700 exploitable, and should I be worried? Whether CVE-2024-2700 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-2700 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-2700?
- Upgrade
io.quarkus:quarkus-coreto 3.9.2 or later - Upgrade
io.quarkus:quarkus-coreto 3.8.4 or later - Upgrade
io.quarkus:quarkus-coreto 3.2.12.Final or later
- Upgrade