CVE-2022-35827
Visual Studio Remote Code Execution Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 17.2.7, 17.0.13, 15.9.50, 14.0.27552.0, 16.11.18, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Visual Studio Remote Code Execution Vulnerability
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Microsoft Microsoft Visual Studio 2022 version 17.2
From 17.2.0 · fixed in 17.2.7
- Microsoft Microsoft Visual Studio 2022 version 17.0
From 17.0.0 · fixed in 17.0.13
- Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
From 15.9.0 · fixed in 15.9.50
- Microsoft Microsoft Visual Studio 2015 Update 3
From 14.0.0 · fixed in 14.0.27552.0
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
From 16.11.0 · fixed in 16.11.18
- Microsoft Microsoft Visual Studio 2019 version 16.9 (includes 16.0 - 16.8)
From 15.0.0 · fixed in 16.9.24
- Microsoft Microsoft Visual Studio 2013 Update 5
From 12.0.0 · fixed in 12.0.40699.0
- Microsoft Microsoft Visual Studio 2012 Update 5
From 11.0.0 · fixed in 11.0.61252.0