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
- 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
Summary
<p>A remote code execution vulnerability exists in Visual Studio when it improperly handles objects in memory. 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>To exploit the vulnerability, an attacker would have to convince a user to open a specially crafted file with an affected version of Visual Studio.</p> <p>The update addresses the vulnerability by correcting how Visual Studio handles objects in memory.</p>
Timeline
- CVE published
- Record last updated
Affected versions
- Microsoft Microsoft Visual Studio 2019 version 16.7 (includes 16.0 – 16.6)
From 16.0.0
- Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
From 15.9.0
- Microsoft Microsoft Visual Studio 2019 version 16.0
From 16.0
- Microsoft Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3)
From 16.0
- Microsoft Microsoft Visual Studio 2012 Update 5
From 11.0.0
- Microsoft Microsoft Visual Studio 2013 Update 5
From 12.0.0
- Microsoft Microsoft Visual Studio 2015 Update 3
From 14.0.0