Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2020-0787: Windows BITS Symbolic Link Privilege Escalation

Published Mar 12, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS42.5%99th percentile
CISA KEVYesAdded Jan 28, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2020-0787CWE-59 · Improper Link Resolution Before…

CVE-2020-0787 is a local privilege escalation vulnerability in the Windows Background Intelligent Transfer Service (BITS). Improper handling of symbolic links allows an attacker with existing code execution on an affected system to elevate privileges and execute arbitrary code as SYSTEM. Exploitation has been observed in Maze and Egregor ransomware campaigns, including use of the SOURBITS exploit utility by UNC2198.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation elevates an attacker's execution context to SYSTEM, allowing arbitrary code execution with system-level privileges. The vulnerability has been used for post-compromise privilege escalation in ransomware intrusions.

Mitigation

If you can’t patch tonight, do this now.

If remediation cannot be completed immediately, investigate affected systems for evidence of compromise and initiate incident response and recovery if compromise is identified. No vulnerability-specific workaround is established by the available information.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates addressing CVE-2020-0787 to affected Windows systems. Prioritize remediation because the vulnerability has been exploited in the wild. Specific affected versions and update identifiers are not available in the supplied information.

Public exploits

Exploits

3 exploits validated by Mallory's analysis.

View more in app →
cve_2020_0787_bits_arbitrary_file_move.rbThis repository contains a single Metasploit module implementing a local privilege escalation exploit for CVE-2020-0787, targeting Windows 10 and Windows Server 2016 and later. The exploit abuses an arbitrary file move vulnerability in the Background Intelligent Transfer Service (BITS) to overwrite the system DLL 'C:\Windows\System32\WindowsCoreDeviceInfo.dll' with a malicious DLL generated by Metasploit. The Update Session Orchestrator service is then triggered to load the malicious DLL, resulting in code execution as SYSTEM. The module is weaponized, supporting customizable payloads (such as Meterpreter) and includes cleanup routines. The exploit requires a Meterpreter session on a vulnerable system and is only effective on Windows 10/Server 2016+ where the Update Session Orchestrator service is present. The main fingerprintable endpoint is the system DLL path that is overwritten. The code is well-structured, leverages multiple Metasploit mixins, and provides options for controlling DLL overwrite and job timing.Disclosed Mar 10, 2020 · Framework: metasploit · ruby · localWeaponizedCVE-2020-0787-EXP-ALL-WINDOWS-VERSIONThis repository implements a local privilege escalation exploit for CVE-2020-0787, targeting all supported versions of Microsoft Windows. The exploit leverages the Background Intelligent Transfer Service (BITS) and a series of mount point and symbolic link manipulations to move an attacker-controlled file (such as a DLL) into a protected directory (e.g., C:\Windows\System32) with SYSTEM privileges. The repository is structured as a Visual Studio solution with three main projects: the core exploit logic (BitsArbitraryFileMove), a utility library (CommonUtils), and an exploit runner (BitsArbitraryFileMoveExploit). The exploit works by preparing a workspace, creating mount points and symlinks, setting oplocks, and manipulating BITS jobs to achieve the file move as SYSTEM. The code is written in C++ and is operational, providing a working exploit chain rather than just a proof of concept. The main entry points are BitsArbitraryFileMove.cpp and BitsArbitraryFileMoveExploit.cpp. The exploit requires local access and sufficient privileges to create directories and symlinks, and it targets the Windows platform broadly. No network endpoints are involved; all actions are performed locally on the filesystem and via Windows internal object manager paths.cbwang505 · Disclosed Jun 16, 2020 · c++ · header · localOperationalCVE-2020-0787This repository contains a C++ exploit for CVE-2020-0787, a vulnerability in the Microsoft Windows Background Intelligent Transfer Service (BITS) that allows for arbitrary file move operations with SYSTEM privileges. The exploit is structured as a Visual Studio solution with three main projects: BitsArbitraryFileMove (core logic), BitsArbitraryFileMoveExploit (exploit entry point), and CommonUtils (utility functions for file and symlink manipulation). The exploit works by creating a workspace with specific directories and files, setting up mount points and symlinks, and abusing BITS jobs to move an attacker-controlled file (such as a DLL) into a protected system directory (e.g., C:\Windows\System32). This can be used for privilege escalation or arbitrary code execution as SYSTEM. The README provides usage examples, including executing arbitrary commands via named pipes and running a payload executable. The code is operational and provides a working exploit chain for local privilege escalation on Windows systems vulnerable to CVE-2020-0787.yanghaoi · Disclosed Nov 16, 2021 · c++ · header · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1709operating_system
Microsoft CorporationWindows 10 1803operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 1903operating_system
Microsoft CorporationWindows 10 1909operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 1803operating_system
Microsoft CorporationWindows Server 1903operating_system
Microsoft CorporationWindows Server 1909operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
FAQ

Frequently asked questions

Is CVE-2020-0787 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 28, 2022.
Is there a public exploit for CVE-2020-0787?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2020-0787, the earliest disclosed Mar 10, 2020.
Is there a patch for CVE-2020-0787?
Apply the Microsoft security updates addressing CVE-2020-0787 to affected Windows systems. Prioritize remediation because the vulnerability has been exploited in the wild.
What products are affected by CVE-2020-0787?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1709, Microsoft Corporation Windows 10 1803, Microsoft Corporation Windows 10 1809, and 12 more.
How severe is CVE-2020-0787?
CVE-2020-0787 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 42.5% (99th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence3Every report linking this CVE to a named adversary.
Associated malware9Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.