Loading vulnerability…
CVE-2020-7012 is a prototype pollution vulnerability in Kibana's Upgrade Assistant affecting versions 6.7.0 through 6.8.8 and 7.0.0 through 7.6.2. An authenticated attacker with privileges to write to the Kibana index can insert crafted data that pollutes object prototypes within the application, leading Kibana to execute arbitrary code. Successful exploitation may result in code execution in the context of the Kibana process on the underlying host system.
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 single Metasploit module targeting CVE-2020-7012, a prototype pollution vulnerability in Kibana's Upgrade Assistant (prior to version 7.6.3). The exploit allows remote code execution by polluting the JavaScript prototype chain, enabling arbitrary command execution on the server. The module supports two attack vectors: directly targeting the ElasticSearch backend or using Kibana's developer console. It requires network access to the target's HTTP interface (default ports 5601 for Kibana, 9200 for ElasticSearch), and may require authentication if enabled. The default payload is a reverse shell, but any Metasploit-compatible payload can be used. The module includes cleanup routines to remove malicious indices and restore Kibana functionality. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.