CVE-2020-1416

An elevation of privilege vulnerability exists in Visual Studio and Visual Studio Code when they load software dependencies, aka 'Visual Studio and Visual Studio Code Elevation of Privilege Vulnerability'.

Published: 2020-07-14 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-1416 is rated Moderate Risk (63.5/100): CVSS High severity, with high exploitation likelihood (EPSS 5.86%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-1416

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 9.87% 5.86% -4.01%
2 2026-03-22 9.80% 9.87% +0.08%
3 2026-03-11 — 9.80% —

Full EPSS history (32 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-1416

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.6 10.0 [email protected]

Weakness enumeration for CVE-2020-1416

Affected software / configurations for CVE-2020-1416

Vendor Product Version Raw CPE
microsoft azure_storage_explorer — cpe:2.3:a:microsoft:azure_storage_explorer:-:*:*:*:*:*:*:*
microsoft typescript — cpe:2.3:a:microsoft:typescript:-:*:*:*:*:*:*:*
microsoft visual_studio_2017 >= 15.0, < 15.9.25 cpe:2.3:a:microsoft:visual_studio_2017:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.0, < 16.0.16 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.1, < 16.4.11 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.5, < 16.6.4 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft visual_studio_code < 1.47.1 cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*

References for CVE-2020-1416

cvelogic Threat Intelligence