Loading vulnerability…
The Marathon UI in DC/OS versions prior to 1.9.0 permits unauthenticated users to deploy arbitrary Docker containers. The flaw stems from improper restriction of container volume mount configurations, allowing an attacker to specify a bind mount of the host root filesystem (/) into the deployed container with read/write access. If the attacker supplies a malicious Docker image, the container can modify sensitive host paths such as /etc/cron.d/, resulting in execution of attacker-controlled commands on the underlying host as root. The issue affects environments where the Docker daemon accepts Marathon-provided container configuration without additional policy enforcement.
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 (modules/exploits/linux/http/dcos_marathon.rb) that exploits a vulnerability in Mesosphere DC/OS Marathon (CVE-2017-20198). The exploit abuses the Marathon UI's ability to deploy Docker containers, creating a container with the host root filesystem mounted read/write. It writes a cron job to /etc/cron.d/ on the host, which executes a Python payload (provided by the attacker) as root. The module interacts with the Marathon API (default port 8080, endpoint /v2/apps) to create and manage the malicious container. The exploit is operational and allows for arbitrary code execution as root on the host, provided the attacker can reach the Marathon UI and the cluster has available resources. The code is written in Ruby and is designed to be used within the Metasploit framework.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.