Loading vulnerability…
InfluxDB OSS 2.x through version 2.7.11 stores the administrative operator token under the default organization. Consequently, an authorized user who has read access to the authorization resource of that default organization can retrieve the operator token. InfluxDB OSS 1.x, InfluxDB Enterprise, InfluxDB Cloud, Cloud Dedicated, and Clustered deployments are not affected. InfluxDB OSS 2.8.0 addresses the issue.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository provides a proof-of-concept (PoC) exploit for CVE-2024-30896, a privilege escalation vulnerability in InfluxDB. The exploit consists of a Python script ('influxdbPrivescCVE_PoC_Script.py') and a requirements file specifying the needed Python package ('influxdb_client'). The script allows an attacker with a valid allAccess token to connect to a target InfluxDB instance (specified via the '-e' argument), enumerate all authorization tokens, and extract those with operator-level (admin) permissions. This enables privilege escalation from an organizational user to an operator, potentially compromising the entire InfluxDB instance. The README.md provides detailed background, usage instructions, exploitation scenarios (via API and CLI), and mitigation recommendations. The exploit is network-based, requiring access to the InfluxDB API endpoint, and is a functional PoC rather than a weaponized or framework-based exploit.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.