Loading vulnerability…
CVE-2024-2700 is a configuration-property leakage vulnerability in Quarkus Core. During application builds, Quarkus captures environment variables and .env values in the quarkus.* configuration namespace. The resulting built application inherits these build-time values at runtime unless they are explicitly overridden. Application-specific configuration namespaces are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information-disclosure vulnerability in quarkus-core that can leak local configuration properties into Quarkus applications.
A Quarkus Core information-disclosure vulnerability that can leak local configuration properties into Quarkus applications.
A Quarkus Core vulnerability that can leak local configuration properties into Quarkus applications.
A Quarkus Core vulnerability that can leak local configuration properties into Quarkus applications. It is addressed in Red Hat build of Quarkus 3.8.4.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.