Skip to content
Fencer Intel
medium 5.5

CVE-2020-17100 json

Visual Studio Tampering Vulnerability

published 5y ago modified 4mo ago also EUVD-2020-9055

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

Visual Studio Tampering Vulnerability

Patch / fix

Is CVE-2020-17100 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
  • Microsoft Microsoft Visual Studio 2019 version 16.0
  • Microsoft Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3)
  • Microsoft Microsoft Visual Studio 2019 version 16.7 (includes 16.0 – 16.6)
  • Microsoft Microsoft Visual Studio 2019 version 16.8

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.