Skip to content
Server Security Center
KEVhigh7.8

CVE-2020-0683: Microsoft Windows Installer Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CISA ADP)
7.8
high
EPSS (exploit probability, 30 days)
7.7%
higher than 94.7% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2020-0683 explained

CVE-2020-0683 is an elevation of privilege vulnerability in the Windows Installer in Microsoft Windows. It occurs when MSI packages process symbolic links, a link-following weakness. CISA lists it as known to be exploited, so unpatched Windows clients and servers face a real risk of local attackers gaining higher privileges.

Impact

An attacker who can already run code on a system with low privileges can elevate those privileges. No user interaction is needed. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so each attack requires manual steps on a target. The attack is local, not remote over the network.

Who is affected

The CVE record lists many Microsoft Windows releases. Examples include 7 for x64-based Systems Service Pack 1, 8.1 for x64-based systems, RT 8.1 and 10 for x64-based Systems, with more entries shown on the page. Microsoft Windows Server is affected across 13 listed models plus Core installation entries. Windows 10 Version 1903 and 1909 editions and their Server Core counterparts are also listed. The CVE record names no fixed version.

Written with AI from the data on this page and checked against it automatically.

Official description

An elevation of privilege vulnerability exists in the Windows Installer when MSI packages process symbolic links, aka 'Windows Installer Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2020-0686.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows
    Affected
    • 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.1
    • 10 for 32-bit Systems
    • 10 for x64-based Systems
    • 10 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 Version 1607 for 32-bit Systems
    • 10 Version 1607 for x64-based Systems
    Fixed in
    not stated
  • Microsoft Windows Server
    Affected
    • 13 listed models (2008 for Itanium-Based Systems Service Pack 2 … 2019 (Core installation))
    • version 1803 (Core Installation)
    • 2008 for 32-bit Systems Service Pack 2 (Core installation)
    • 2008 for x64-based Systems Service Pack 2 (Core installation)
    • 2008 R2 for x64-based Systems Service Pack 1 (Core installation)
    all 13 listed versions
    • 2008 for Itanium-Based Systems Service Pack 2
    • 2008 for x64-based Systems Service Pack 2
    • 2008 for 32-bit Systems Service Pack 2
    • 2008 R2 for Itanium-Based Systems Service Pack 1
    • 2008 R2 for x64-based Systems Service Pack 1
    • 2012
    • 2012 (Core installation)
    • 2012 R2
    • 2012 R2 (Core installation)
    • 2016
    • 2016 (Core installation)
    • 2019
    • 2019 (Core installation)
    Fixed in
    not stated
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1903 for x64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server, version 1903 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1909 for 32-bit Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1909 for x64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1909 for ARM64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server, version 1909 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's security updates for CVE-2020-0683 to all affected Windows and Windows Server systems, following the vendor advisory.
  2. Prioritize systems where many users have local accounts, such as shared servers and terminal hosts.
  3. Limit local logon rights and remove unnecessary low-privilege accounts to reduce who can attempt local privilege escalation.
  4. Check systems for signs of compromise, such as unexpected privileged accounts or unexplained software installations.
  5. Replace Windows releases that no longer receive security updates from Microsoft.

The CVE record names no fixed version, but this does not mean no fix exists. Follow the Microsoft advisory to identify the correct update for each Windows release. CISA's required action is to apply updates per vendor instructions. Until updates are installed, restrict local access and monitor for suspicious privilege changes.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2020-0683

Can this be exploited remotely?
No. The attack vector is local. An attacker needs existing low-privilege access to the system, but no user interaction is required.
Is CVE-2020-0683 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Whether it is used in ransomware campaigns is listed as unknown.
What does CISA require?
CISA's required action is to apply updates per vendor instructions. Use the Microsoft advisory to find the update for each affected release.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.