CVE-2019-1351: High severity visual studio professional 2017 vulnerability

Published Jan 24, 2020
·
Updated

A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

Affected Software

3 affected components
Microsoft Visual Studio 2017>=15.0<15.9.18
Microsoft Visual Studio 2019>=16.0<16.4.1
openSUSE Leap=15.1

Event History

Jan 24, 2020
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2019-1351?

CVE-2019-1351 is rated as a medium severity vulnerability.

2

How do I fix CVE-2019-1351?

To fix CVE-2019-1351, apply the latest updates for Microsoft Visual Studio as recommended in the official security advisories.

3

Which versions of Visual Studio are affected by CVE-2019-1351?

CVE-2019-1351 affects Microsoft Visual Studio 2017 versions prior to 15.9.18 and Microsoft Visual Studio 2019 versions prior to 16.4.1.

4

What type of vulnerability is CVE-2019-1351?

CVE-2019-1351 is characterized as a tampering vulnerability related to improper handling of virtual drive paths.

5

Are any other platforms affected by CVE-2019-1351?

In addition to Microsoft Visual Studio, openSUSE Leap 15.1 is also affected by CVE-2019-1351.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203