CVE-2024-45737 is a cross-site request forgery vulnerability affecting Splunk Enterprise before 9.1.6, 9.2.3, and 9.3.1, and Splunk Cloud Platform before 9.1.2312.204 and 9.2.2403.108. The flaw allows a low-privileged authenticated Splunk user who does not have the admin or power roles to change the maintenance mode state of the App Key Value Store (KVStore). The vulnerable behavior is exposed through the KVStore maintenance mode change functionality, which can be triggered via crafted web requests without adequate CSRF protection. Successful exploitation results in unauthorized state changes to the KVStore maintenance mode despite the attacker lacking the intended privilege level for that administrative action.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.