Loading vulnerability…
CVE-2019-5475 is a remote code execution vulnerability in the Nexus Yum Repository Plugin v2. The vulnerability arises when the CommandLineExecutor.java component is supplied with untrusted or malicious data, such as through the Yum Configuration Capability, allowing attackers to execute arbitrary commands on the 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 provides a proof-of-concept (PoC) and testbed for exploiting CVE-2019-5475 and CVE-2019-15588, which are command injection (RCE) vulnerabilities in the Yum Repository plugin of Sonatype Nexus Repository Manager 2.x. The exploit requires admin access (default credentials are often unchanged) and targets the 'createrepo' or 'mergerepo' path fields in the Nexus GUI, which are vulnerable to command injection. The repository includes a Docker-based environment with two vulnerable Nexus instances (2.14.9 and 2.14.14) and an attacker machine. The Java code in 'nexus-yum-core' simulates the vulnerable backend logic and demonstrates how arbitrary commands, including reverse shell payloads, can be injected and executed. The main exploit capability is remote code execution, allowing an attacker to gain shell access to the server. The repository is structured for easy testing and validation of the exploit, with clear instructions and sample payloads provided in the README.
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.