CVE-2020-7384 is a command injection vulnerability in the Metasploit Framework's msfvenom tool, specifically when processing crafted APK files as Android payload templates. The vulnerability exists in Metasploit Framework versions up to 6.0.11 and Metasploit Pro up to 4.18.0 on Linux and macOS. The flaw arises from improper handling of the APK's signature "Owner" field, which is unsafely passed to a shell command (keytool) without sanitization, allowing arbitrary command execution. The vulnerable code resides in msf/core/payload/apk.rb. The issue does not affect Windows due to broken APK template support on that platform.
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 contains a single Metasploit exploit module targeting a command injection vulnerability (CVE-2020-7384) in the msfvenom payload generator of the Metasploit Framework and Metasploit Pro. The exploit works by generating a specially crafted APK file with a malicious X.509 certificate Common Name field. When this APK is used as a template with msfvenom's -x option, arbitrary shell commands embedded in the certificate are executed on the system running msfvenom. The module is written in Ruby and leverages Metasploit's FILEFORMAT exploit mixin. The only file in the repository is the exploit module itself, which generates the malicious APK file (default name: msf.apk). The attack vector is local, as it targets users who run msfvenom with a crafted file. No network endpoints are involved. The exploit is operational, as it provides a working payload for command execution, but is not weaponized for mass exploitation.
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.