First published: Tue Aug 09 2022(Updated: )
Visual Studio Remote Code Execution Vulnerability
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
Microsoft Visual Studio 2012 | =5 | |
Microsoft Visual Studio 2015 | =3 | |
Microsoft Visual Studio 2017 (includes 15.0 - 15.8) | =15.9 | |
Microsoft Visual Studio 2019 (includes 16.0 - 16.10) | =16.11 | |
Microsoft Visual Studio 2019 (includes 16.0 - 16.8) | =16.9 | |
Microsoft Visual Studio 2013 | =5 | |
Microsoft Visual Studio 2022 | =17.2 | |
Microsoft Visual Studio 2022 | =17.0 | |
Microsoft Visual Studio | =2012-update_5 | |
Microsoft Visual Studio | =2013-update_5 | |
Microsoft Visual Studio | =2015-update3 | |
Microsoft Visual Studio 2017 | =15.9 | |
Microsoft Visual Studio 2019 | =16.9 | |
Microsoft Visual Studio 2019 | =16.11 | |
Microsoft Visual Studio 2022 | =17.0 | |
Microsoft Visual Studio 2022 | =17.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-35827 is a remote code execution vulnerability in Visual Studio.
CVE-2022-35827 has a severity rating of 8.8 (high).
CVE-2022-35827 affects Visual Studio 2012 (update 5), Visual Studio 2013 (update 5), Visual Studio 2015 (update 3), Visual Studio 2017 (version 15.9), Visual Studio 2019 (versions 16.9 and 16.11), and Visual Studio 2022 (versions 17.0 and 17.2).
To fix CVE-2022-35827, you should apply the corresponding patches or updates provided by Microsoft for your specific version of Visual Studio. Links to the patches and updates can be found in the Microsoft Security Response Center (MSRC) update guide for CVE-2022-35827.
More information about CVE-2022-35827 can be found in the Microsoft Security Response Center (MSRC) update guide for CVE-2022-35827.