Loading vulnerability…
Docker Desktop Community Edition versions before 2.1.0.1 improperly allow a low-privileged local user to place a malicious docker-credential-wincred executable in a Docker Desktop version-bin directory under the system-wide ProgramData location. When an administrator or service-context user subsequently authenticates with Docker, restarts Docker, or performs a Docker login, Docker can execute the attacker-controlled credential-helper binary.
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/windows/local/docker_credential_wincred.rb) that exploits a privilege escalation vulnerability (CVE-2019-15752) in Docker Desktop Community Edition for Windows versions prior to 2.1.0.1. The exploit works by uploading a malicious executable (payload) to the DockerDesktop version-bin directory, specifically as 'docker-credential-wincred.exe'. When the Docker user next logs in, this payload is executed, allowing the attacker to escalate privileges. The module checks for the presence of a vulnerable Docker version and appropriate UAC settings before proceeding. The exploit is operational and requires a low-privileged session on the target. The only fingerprintable endpoint is the file path where the payload is dropped. The code is written in Ruby and is designed to be used within the Metasploit 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.
1 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.