Vulnerability in Microsoft Visual Studio 2017
CVE-2019-1351
A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.
EPSS: 0.087 (94.6th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
Affected products
- Microsoft Visual Studio 2017 — versions 15.0
- Microsoft Visual Studio 2017 Version 15.9 (Includes 15.1 - 15.8) — versions unspecified
- Microsoft Visual Studio 2019 — versions 16.0
- Microsoft Visual Studio 2019 Version 16.4 (Includes 16.0 - 16.3) — versions unspecified
- Microsoft Visual_studio_2017
- Microsoft Visual_studio_2019
- Opensuse Leap — versions 15.1
Weakness classification (CWE)
Public proof-of-concept exploits
References
- secure@microsoft.com (Patch, x_refsource_MISC, Vendor Advisory)
- secure@microsoft.com (x_refsource_MISC)
- secure@microsoft.com (vendor-advisory, Third Party Advisory, x_refsource_SUSE)
- secure@microsoft.com (vendor-advisory, x_refsource_GENTOO)
- secure@microsoft.com (vendor-advisory, x_refsource_SUSE)
Frequently asked questions
- What is CVE-2019-1351?
- CVE-2019-1351 is a high-severity vulnerability in Microsoft Visual Studio 2017, classified under Use of Incorrectly-Resolved Name or Reference. CVSS score: 7.5/10. Published 2020-01-24.
- How severe is CVE-2019-1351?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2019-1351 known to be exploited?
- 13 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.