# CVE-2020-0787: Microsoft Windows Background Intelligent Transfer Service (BITS) Improper Privilege Management

> An attacker can exploit improper symbolic link handling in Windows BITS to elevate privileges on affected systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Jan 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Mar 2020
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-2ffp-p9mj-92cf

## What is CVE-2020-0787?

CVE-2020-0787 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 12 Mar 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An elevation of privilege vulnerability exists when the Windows Background Intelligent Transfer Service (BITS) improperly handles symbolic links, aka 'Windows Background Intelligent Transfer Service Elevation of Privilege Vulnerability'.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2020-0787?

It affects 17 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1709, Microsoft Windows 10 1803, Microsoft Windows 10 1809, Microsoft Windows 10 1903, Microsoft Windows 10 1909, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 1803, Microsoft Windows Server 1903, Microsoft Windows Server 1909, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

## How do I fix CVE-2020-0787?

No fix has been published for CVE-2020-0787 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Jul 2022.

## Is CVE-2020-0787 being exploited?

Yes. Attackers have exploited CVE-2020-0787 in the wild since at least 28 Jan 2022, including in ransomware campaigns.

Public exploit code:

- Support ALL Windows Version (github_poc): https://github.com/cbwang505/CVE-2020-0787-EXP-ALL-WINDOWS-VERSION
- CVE-2020-0787的简单回显 (github_poc): https://github.com/yanghaoi/CVE-2020-0787
- Background Intelligent Transfer Service Arbitrary File Move Privilege Elevation Vulnerability (metasploit)

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-0787 and fix it if it is affected.

What it is: CVE-2020-0787 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 12 Mar 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2020-0787 in the wild since at least 28 Jan 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-0787/ (Markdown: https://insights.sbomify.com/CVE-2020-0787/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-0787
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-0787
- OSV: https://osv.dev/vulnerability/CVE-2020-0787

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-0787/
Summaries are generated and may contain mistakes; the official description above is the record.