LiveActive security incident?Get immediate response
CVE Record

CVE-2020-0787: An elevation of privilege vulnerability exists when the Windows Background Intelligent Transfer Service (BI...

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'.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Windows BITS can let an attacker abuse symbolic links to elevate privileges after reaching a vulnerable system. Successful exploitation could severely affect confidentiality, integrity, and availability. Because CISA lists this vulnerability as known exploited, unremediated affected Windows endpoints and servers warrant prompt attention.

Executive priority

Treat as a high-priority remediation item because exploitation is documented through CISA KEV and successful abuse can produce high business impact. Focus first on vulnerable high-value systems and unsupported releases. This vulnerability does not, by itself, establish a remote compromise path, but it can materially amplify an existing intrusion.

Technical view

CVE-2020-0787 is a CWE-59 symbolic-link handling vulnerability in Windows Background Intelligent Transfer Service. It has CVSS 3.1 score 7.8 with a local, low-complexity vector and user interaction required. The supplied record covers numerous Windows client and server releases, including Windows 7 through 10 and Windows Server 2008 through 2019.

Likely exposure

Exposure is likely where listed Windows client or server versions remain installed without the applicable Microsoft remediation. Risk is especially relevant on endpoints where an attacker can obtain local execution or induce required user interaction. The bundle does not provide build-level fixed-version details, so patch status must be confirmed against Microsoft guidance.

Exploitation context

CISA KEV inclusion supports active exploitation in the wild. This is an elevation-of-privilege issue rather than a demonstrated remote entry point; an attacker would generally need an existing foothold and the required user interaction. The supplied sources do not describe campaign scope, exploitation frequency, or specific threat actors.

Researcher notes

The core condition is improper symbolic-link handling by BITS, mapped to CWE-59. CVSS indicates local access, low complexity, no privileges, required user interaction, unchanged scope, and high impact across all three security objectives. The bundle lacks fixed build numbers, detection signatures, exploit-chain details, and campaign telemetry; consult Microsoft for precise remediation applicability.

Mitigation direction

  • Apply the applicable Microsoft security update after confirming affected Windows versions and build requirements.
  • Prioritize internet-facing, privileged, shared, and high-value Windows systems in remediation scheduling.
  • Retire or isolate unsupported Windows releases when Microsoft updates are unavailable.
  • Use endpoint controls to reduce initial compromise and unauthorized local execution opportunities.

Validation and detection

  • Inventory Windows editions, versions, architectures, installation types, and current security update levels.
  • Compare each system's build and patch history with Microsoft's CVE-2020-0787 guidance.
  • Confirm remediation deployment succeeded and investigate update failures or excluded systems.
  • Review endpoint telemetry for suspicious privilege changes and symbolic-link-related activity around BITS.
  • Document unsupported or unpatchable systems, compensating controls, ownership, and retirement dates.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-59: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-0787 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-0787Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  4. ADP timelineCISA-ADP

    CVE-2020-0787 added to CISA KEV

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvcother:kev
  • 2022-01-28T00:00:00.000Z: CVE-2020-0787 added to CISA KEV
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1709 for 32-bit Systems, 10 Version 1709 for x64-based Systems, 10 Version 1709 for ARM64-based Systems, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1, 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1Listed
MicrosoftWindows Serverversion 1803 (Core Installation), 2019, 2019 (Core installation), 2016, 2016 (Core installation), 2008 for 32-bit Systems Service Pack 2, 2008 for 32-bit Systems Service Pack 2 (Core installation), 2008 for Itanium-Based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation)Listed
MicrosoftWindows 10 Version 1909 for 32-bit SystemsunspecifiedListed
MicrosoftWindows 10 Version 1909 for x64-based SystemsunspecifiedListed
MicrosoftWindows 10 Version 1909 for ARM64-based SystemsunspecifiedListed
MicrosoftWindows Server, version 1909 (Server Core installation)unspecifiedListed
MicrosoftWindows 10 Version 1903 for 32-bit SystemsunspecifiedListed
MicrosoftWindows 10 Version 1903 for x64-based SystemsunspecifiedListed
MicrosoftWindows 10 Version 1903 for ARM64-based SystemsunspecifiedListed
MicrosoftWindows Server, version 1903 (Server Core installation)unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-59 · source CWE mapping

Improper Link Resolution Before File Access ('Link Following')

Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.