CVE-2018-1111, also known as DynoRoot, is a command injection vulnerability in DHCP packages on Red Hat Enterprise Linux 6 and 7 and Fedora 28 and earlier. The flaw resides in the NetworkManager integration script included with the DHCP client, where untrusted data received from DHCP responses is insufficiently sanitized before being incorporated into a shell execution context. A malicious DHCP server, or an attacker on the local network capable of spoofing DHCP replies, can supply crafted DHCP option data that causes arbitrary commands to be executed by the vulnerable script. Because the affected integration runs with elevated privileges during network configuration, successful exploitation can result in command execution as root on systems that use NetworkManager and obtain configuration via DHCP.
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 module: 'rhel_dhcp_client_command_injection.rb', which exploits the DynoRoot vulnerability (CVE-2018-1111) in the DHCP client integration script used by Red Hat Enterprise Linux 6/7 and Fedora 28/earlier. The exploit works by acting as a malicious DHCP server and injecting a crafted DHCP option that results in arbitrary command execution as root on vulnerable systems using NetworkManager and DHCP. The module is operational, allowing the attacker to specify a payload (arbitrary command) that is delivered via a DHCP response. The attack vector is network-based, requiring the attacker to be able to serve or spoof DHCP responses on the local network. The only fingerprintable endpoint is the DHCP server functionality itself. 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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.