Visual Studio Remote Code Execution Vulnerability
CVE-2020-17156
Security VulnerabilityReleased: Dec 8, 2020
- Assigning CNA
- Microsoft
- CVE.org link
- CVE-2020-17156
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
How could an attacker exploit this vulnerability?
To exploit this vulnerability, an attacker would need to convince a targeted user to clone a malicious repository from inside Visual Studio. Attacker-specified code would execute during the clone operation.
Acknowledgements
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information.
Security Updates
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.
Release date Descending
Product
Platform
Impact
Max Severity
Article
Download
Build Number
Dec 8, 2020
Microsoft Visual Studio 2019 version 16.7 (includes 16.0 – 16.6)
-
Remote Code Execution
Important
- -
Dec 8, 2020
Microsoft Visual Studio 2019 version 16.8
-
Remote Code Execution
Important
- -
Dec 8, 2020
Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3)
-
Remote Code Execution
Important
- -
Dec 8, 2020
Microsoft Visual Studio 2019 version 16.0
-
Remote Code Execution
Important
- -
Dec 8, 2020
Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
-
Remote Code Execution
Important
- -
All results loaded
Loaded all 5 rows
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
version
revisionDate
description
1.0
Dec 8, 2020
Information published.
How satisfied are you with the MSRC Security Update Guide?