CVE-2019-16328 is a remote code execution vulnerability in RPyC versions 4.1.0 and 4.1.1. The vulnerability arises from insecure use of getattr on user-supplied objects and operations, allowing remote attackers to traverse object properties and execute arbitrary commands on the server. Attackers can chain attribute and item lookups to access Python builtins and functions such as os.system, leading to full code execution on the RPyC service with default configuration.
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 is the official Metasploit Framework, a comprehensive and modular exploitation platform widely used for penetration testing, vulnerability research, and exploit development. The structure includes configuration files, Ruby application code, data files for exploits (including CVE-specific resources), and various templates and binaries for testing and exploitation. The framework supports a vast array of exploits, payloads, and auxiliary modules, enabling both network-based and local attacks against a wide range of targets. The presence of files such as 'data/exploits/CVE-2008-6508/plugin.xml', 'data/exploits/CVE-2010-1240/template.pdf', and 'data/exploits/CVE-2012-0013/docProps/core.xml' indicates support for specific CVEs, while the overall structure and codebase are designed for extensibility and integration with new exploits and payloads. The repository is weaponized, as it allows users to easily select, configure, and launch exploits with customizable payloads. No hardcoded network endpoints (such as IPs or domains) are present in the analyzed files, but numerous file-based and configuration endpoints are used throughout the 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.