CVE-2022-35777: Visual Studio Remote Code Execution Vulnerability
Published Aug 9, 2022
·Updated
Visual Studio Remote Code Execution Vulnerability
Affected Software
15 affected componentsFixes available
Microsoft Visual Studio 2012=5
Microsoft Visual Studio 2019 (includes 16.0 - 16.8)=16.9
Microsoft Visual Studio 2019 (includes 16.0 - 16.10)=16.11
Microsoft Visual Studio 2017 (includes 15.0 - 15.8)=15.9
Microsoft Visual Studio 2015=3
Microsoft Visual Studio 2013=5
Microsoft Visual Studio=2012-update_5
Microsoft Visual Studio=2013-update_5
Microsoft Visual Studio=2015-update3
Microsoft Visual Studio 2017>=15.0<=15.9
Microsoft Visual Studio 2019>=16.0<=16.11
Microsoft Visual Studio 2022=17.0
Microsoft Visual Studio 2022=17.2
Microsoft Visual Studio 2022=17.2
Microsoft Visual Studio 2022=17.0
Event History
Aug 9, 2022
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·07:59 PM
Data Sourced
via MITRE·07:59 PM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2022-35777?
The severity of CVE-2022-35777 is high, with a CVSS score of 8.8.
2
Which versions of Microsoft Visual Studio are affected by CVE-2022-35777?
Microsoft Visual Studio versions 2012, 2013, 2015, 2017, 2019, and 2022 are affected by CVE-2022-35777.
3
How can I fix CVE-2022-35777?
To fix CVE-2022-35777, apply the relevant patches or updates provided by Microsoft for your specific version of Visual Studio.
4
Where can I find more information about CVE-2022-35777?
You can find more information about CVE-2022-35777 on the Microsoft Security Response Center website.
5
Are there any workarounds available for CVE-2022-35777?
No specific workarounds have been provided for CVE-2022-35777. It is recommended to apply the patches or updates as soon as possible.