Apache NiFi 1.10.0 through 2.0.0 does not perform fine-grained authorization checks for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers when a user creates a Process Group. A user permitted to create Process Groups can bind a Parameter Context without its authorization being checked when the Process Group does not reference Parameter values, allowing download of non-sensitive Parameter values. The user can also reference otherwise unauthorized Controller Services or Parameter Providers.
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.
This repository contains a Python proof-of-concept exploit for CVE-2024-56512, a vulnerability in Apache NiFi that allows unauthorized access to sensitive API endpoints. The main script, 'Apache_NiFi_Exploit.py', prompts the user for a target NiFi URL and then attempts to access several internal API endpoints without authentication. If successful, it extracts and displays sensitive information such as process group details, configuration, user identities, encryption keys, connection data, system logs, flowfile queues, and version/build information. The exploit demonstrates the risk of improperly secured NiFi deployments and highlights the importance of securing API endpoints. The repository also includes a README, LICENSE, and .gitignore, with the exploit logic entirely contained in the Python script.
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.