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 2019 (includes 16.0 - 16.8) | =16.9 | |
Microsoft Visual Studio 2017 (includes 15.0 - 15.8) | =15.9 | |
Microsoft Visual Studio 2013 | =5 | |
Microsoft Visual Studio 2019 (includes 16.0 - 16.10) | =16.11 | |
Microsoft Visual Studio 2022 | =17.0 | |
Microsoft Visual Studio 2022 | =17.2 | |
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-35826 is a visual Studio remote code execution vulnerability.
CVE-2022-35826 has a severity rating of 8.8 (high).
Visual Studio 2012, Visual Studio 2015, Visual Studio 2019 (16.0 - 16.8), Visual Studio 2017 (15.0 - 15.8), Visual Studio 2013, Visual Studio 2019 (16.0 - 16.10), Visual Studio 2022 (17.0), Visual Studio 2022 (17.2) are affected by CVE-2022-35826.
To fix CVE-2022-35826 in Visual Studio 2012, update to version 5.
To fix CVE-2022-35826 in Visual Studio 2015, update to version 3.
To fix CVE-2022-35826 in Visual Studio 2019 (16.0 - 16.8), refer to the Microsoft support page for the specific remedy.
To fix CVE-2022-35826 in Visual Studio 2017 (15.0 - 15.8), refer to the Microsoft support page for the specific remedy.
To fix CVE-2022-35826 in Visual Studio 2013, update to version 5.
To fix CVE-2022-35826 in Visual Studio 2019 (16.0 - 16.10), refer to the Microsoft support page for the specific remedy.
To fix CVE-2022-35826 in Visual Studio 2022 (17.0), refer to the Microsoft support page for the specific remedy.
To fix CVE-2022-35826 in Visual Studio 2022 (17.2), refer to the Microsoft support page for the specific remedy.