Rapid7 Metasploit Framework versions before 5.0.85 contain an OS command injection vulnerability in the libnotify plugin. The plugin accepts untrusted data in a remote computer hostname or service name. An attacker can craft one of these values, cause it to be imported from a supported source, and trigger command injection on the Metasploit operator's terminal when the operator processes an attacker-supplied file using the db_import command. The issue affects Metasploit Framework and products exposing its plugin system, but not Rapid7 Metasploit Pro.
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 exploit file: 'modules/exploits/unix/fileformat/metasploit_libnotify_cmd_injection.rb'. The module targets a command injection vulnerability (CVE-2020-7350) in the libnotify plugin of the Metasploit Framework (versions 5.0.79 and earlier). The exploit works by generating a malicious XML file (default name: scan.xml) that, when processed by the vulnerable libnotify plugin, injects and executes arbitrary shell commands. The default payload is a Python-based reverse shell, but any Metasploit command payload can be used. The exploit is weaponized, as it is part of the Metasploit framework and allows for customizable payloads. The attack vector is local/fileformat, requiring the target to process the crafted XML file. The only notable endpoints are the generated file (scan.xml) and an example IP address (192.168.20.121) used in the XML content. The repository is structured as a typical Metasploit module and is intended for use within the Metasploit framework.
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.