Git for Visual Studio Tampering Vulnerability
Released: Dec 10, 2019
Last updated: Jan 29, 2020
- Assigning CNA
- Microsoft
- CVE.org link
- CVE-2019-1351
Executive Summary
A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths. An attacker who successfully exploited this vulnerability could write arbitrary files and directories to certain locations on a vulnerable system. However, an attacker would have limited control over the destination of the files and directories.
To exploit the vulnerability, an attacker must clone a file using a specially crafted path on a vulnerable system.
The security update fixes the vulnerability by ensuring Git for Visual Studio properly handles folder paths.
Exploitability
The following table provides an exploitability assessment for this vulnerability at the time of original publication.
- Publicly disclosed
- No
- Exploited
- No
- Exploitability assessment
- Exploitation Less Likely
FAQ
I want to install the latest supported service baseline for Visual Studio. Do I need to install the previous versions first?
No. For both Visual Studio 2019 and Visual Studio 2017, the latest supported servicing baseline is cumulative. For example, if you need to install Visual Studio 2019 version 16.4 you do NOT first have to install any previous versions. See Visual Studio 2019 version 16.4 Release Notes for more information.
Acknowledgements
Security Updates
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.
Disclaimer
Revisions
Updated exploitability assessment for Older Software Release. This is an informational change only.
In the Security Updates table, corrected product name.
Information published.