Unsafe runtime configuration via captured build properties
Published Apr 4, 2024 · Updated Aug 4, 2026
Configuration capture in Red Hat Quarkus allows local users to embed unsafe runtime settings during application builds. The quarkus-core recorder treats local environment, system, Maven, and Gradle properties as build configuration and serializes quarkus.* values into the application. Exploitation requires low-privileged local influence over the build environment; captured test settings can expose data, weaken TLS checks, or delete a database at startup.
Summary
What happened
Configuration capture in Red Hat Quarkus allows local users to embed unsafe runtime settings during application builds. The quarkus-core recorder treats local environment, system, Maven, and Gradle properties as build configuration and serializes quarkus.* values into the application. Exploitation requires low-privileged local influence over the build environment; captured test settings can expose data, weaken TLS checks, or delete a database at startup.
The record
- CVE
- CVE-2024-2700
- Published
- Apr 4, 2024
- Updated
- Aug 4, 2026
- Vendor
- Red Hat
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-526, T1195.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo