Cyber Resilience

CVE-2020-0683

Microsoft Windows 10 1709

CISA KEVActive ExploitationEUVD Exploited
Published
11 February 2020
Modified
29 October 2025
KEV Added
03 November 2021
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.077 94th percentile
Risk Priority 83 floored blend · peak EPSS

Summary

CVE-2020-0683 is a high-severity Link Following (CWE-59) vulnerability in Microsoft Windows 10 1709. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 6% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

An elevation of privilege vulnerability exists in the Windows Installer component when MSI packages process symbolic links. The flaw, tracked as CVE-2020-0683 and distinct from CVE-2020-0686, carries a CVSS 3.1 base score of 7.8 and is associated with CWE-59.

A local attacker with low privileges can exploit the issue without user interaction to obtain elevated rights on an affected system, resulting in full control over confidentiality, integrity, and availability of the host.

Microsoft has published security guidance for the vulnerability, and the flaw appears in CISA's catalog of known exploited vulnerabilities, confirming observed in-the-wild exploitation.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)
KEV Date Added
03 November 2021

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
T1547.009 Shortcut Modification Persistence
Adversaries may create or modify shortcuts that can execute a program during system boot or user login.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2020-0787Same product: Microsoft Windows 10 1507both on KEV
CVE-2019-1130Same product: Microsoft Windows 10 1507both on KEV
CVE-2019-1315Same product: Microsoft Windows 10 1607both on KEV
CVE-2019-1069Same product: Microsoft Windows 10 1507both on KEV
CVE-2020-0638Same product: Microsoft Windows 10 1709both on KEV
CVE-2022-21919Same product: Microsoft Windows 10 1507both on KEV
CVE-2019-1064Same product: Microsoft Windows 10 1607both on KEV
CVE-2021-41379Same product: Microsoft Windows 10 1507both on KEV
CVE-2019-1253Same product: Microsoft Windows 10 1709both on KEV
CVE-2019-1129Same product: Microsoft Windows 10 1709both on KEV

Affected Assets

microsoft
windows 10 1507
all versions
microsoft
windows 10 1607
all versions
microsoft
windows 10 1709
all versions
microsoft
windows 10 1803
all versions
microsoft
windows 10 1809
all versions
microsoft
windows 10 1903
all versions
microsoft
windows 10 1909
all versions
microsoft
windows 7
all versions
microsoft
windows 8.1
all versions
microsoft
windows rt 8.1
all versions
+7 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect link-following flaws before release.

prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

prevents

Secure architecture principles include input validation and safe file-access design patterns.

prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

mitigates

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References