Vulnerabilities · 2019 · Microsoft
CVE-2019-1351
Microsoft Visual Studio 2017 vulnerability
A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.
Affected products
Visual Studio 2017, Visual Studio 2019, Leap. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Microsoft Visual Studio 2017 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1351 · Patch
- lists.opensuse.org/opensuse-security-announce/2020-01/msg00056.html · Third Party Advisory
- lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html
- public-inbox.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/
- security.gentoo.org/glsa/202003-30
- nvd.nist.gov/vuln/detail/CVE-2019-1351
- cve.org/CVERecord?id=CVE-2019-1351
More vulnerabilities in Microsoft products
CVE-2026-85880CVE-2026-81963CVE-2026-69719CVE-2026-69686CVE-2026-69671CVE-2026-69556CVE-2026-62804CVE-2026-32201All 13,589
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.