Visual Studio Remote Code Execution Vulnerability
CVE-2018-8172 is fixed in 7 products on 1 platform, first by KB4342191, released July 10, 2018. It is not reported as exploited. Patch Radar priority: High.
<p>A remote code execution vulnerability exists in Visual Studio software when the software does not check the source code of a file for an unbuilt project. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.</p> <p>Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Visual Studio. In an email attack scenario, an attacker could exploit the vulnerability by sending a specially crafted project, or resource file, to the user and convince the user to open the file.</p> <p>The security update addresses the vulnerability by correcting how Visual Studio checks the source code of a file.</p>
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Microsoft | |||
| Expression Blend 2 Service Pack 2 | KB4342191 | Jul 10, 2018 | |
| Expression Blend 3 Service Pack 1 | KB4342192 | Jul 10, 2018 | |
| Expression Blend 4 Service Pack 3 | KB4342193 | Jul 10, 2018 | |
| Microsoft Visual Studio 2010 Service Pack 1 | KB4336919 | Jul 10, 2018 | |
| Microsoft Visual Studio 2012 Update 5 | KB4336946 | Jul 10, 2018 | |
| Microsoft Visual Studio 2013 Update 5 | KB4336986 | Jul 10, 2018 | |
| Microsoft Visual Studio 2015 Update 3 | KB4336999 | Jul 10, 2018 | |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.