CVE-2019-1351: High severity 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/gitto a version that resolves this vulnerability.Fixed in 2.22.2-r0 - Upgrade
Upgrade
alpine/gitto a version that resolves this vulnerability.Fixed in 2.24.1-r0 - Upgrade
Upgrade
alpine/gitto a version that resolves this vulnerability.Fixed in 2.15.4-r0 - Upgrade
Upgrade
alpine/gitto a version that resolves this vulnerability.Fixed in 2.18.2-r0 - Upgrade
Upgrade
alpine/gitto a version that resolves this vulnerability.Fixed in 2.20.2-r0 - Upgrade
Upgrade
alpine/libgit2to a version that resolves this vulnerability.Fixed in 0.28.4-r0 - Upgrade
Upgrade
alpine/libgit2-1.0to a version that resolves this vulnerability.Fixed in 0.28.4-r0 - Upgrade
Upgrade
alpine/libgit2-1.1to a version that resolves this vulnerability.Fixed in 0.28.4-r0
Event History
Frequently Asked Questions
What is the severity of CVE-2019-1351?
CVE-2019-1351 is rated as a medium severity vulnerability.
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.
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.
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.
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.