Loading vulnerability…
A vulnerability in Docker Desktop for Windows (Enterprise before 2.1.0.9, Stable before 2.2.0.4, Edge before 2.2.2.0) allows local privilege escalation to NT AUTHORITY\SYSTEM. The issue arises from improper handling of diagnostic collection with Administrator privileges, enabling arbitrary DACL permission overwrites and arbitrary file writes.
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 a proof-of-concept (POC) exploit for CVE-2020-10665, a local privilege escalation vulnerability in Docker Desktop for Windows. The exploit is implemented in C++ and consists of a Visual Studio project with source files for utility functions, hardlink creation, and the main exploit logic. The main entry point is 'CVE-2020-10665/CVE-2020-10665.cpp'. The exploit works by: 1. Watching the user's %LOCALAPPDATA%\Temp directory for Docker diagnostic zip files. 2. Triggering Docker Desktop's diagnostic tool to generate such a file. 3. Spraying hardlinks named as expected diagnostic zip files, all pointing to 'PrintConfig.dll' in the Windows system directory. 4. When Docker's diagnostic tool writes to the zip file, it actually overwrites the DLL due to the hardlink, granting the attacker full control over the DLL file. 5. This can be leveraged to escalate privileges to SYSTEM by replacing the DLL with a malicious payload. The exploit targets Docker Desktop for Windows versions prior to the March 2020 Windows cumulative update, which introduced hardlink mitigations. The README provides additional context and references for further privilege escalation using the overwritten DLL. The repository does not contain a weaponized payload but demonstrates the arbitrary file overwrite primitive required for escalation.
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.