All reports
High

quarkus-core leaks local environment variables from Quarkus namespace during application's build

Affected versions

Affected versions
>= 3.9.0.CR1, <= 3.9.1
Fixed version
3.9.2
Affected versions
>= 3.3.0.CR1, <= 3.8.3
Fixed version
3.8.4
Affected versions
< 3.2.12.Final
Fixed version
3.2.12.Final
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-2700

Probability of exploitation in the next 30 days: 0.31%

FIRST EPSS · 2026-11-18

Description

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.

Links

Credits

  • bschuhmann