Vulnerabilities (CVE)

Filtered by vendor Microsoft Subscribe
Filtered by product Visual Studio 2017
Total 82 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-29060 1 Microsoft 3 Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 2024-07-02 N/A 6.7 MEDIUM
Visual Studio Elevation of Privilege Vulnerability
CVE-2019-1211 1 Microsoft 2 Visual Studio 2017, Visual Studio 2019 2024-05-29 3.7 LOW 7.3 HIGH
An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user. To exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands. The update addresses the issue by changing the permissions required to edit configuration files.
CVE-2023-36796 1 Microsoft 16 .net, .net Framework, Visual Studio 2017 and 13 more 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-36794 1 Microsoft 16 .net, .net Framework, Visual Studio 2017 and 13 more 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-36793 1 Microsoft 16 .net, .net Framework, Visual Studio 2017 and 13 more 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-36792 1 Microsoft 16 .net, .net Framework, Visual Studio 2017 and 13 more 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-23381 1 Microsoft 3 Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-21815 1 Microsoft 3 Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-21808 1 Microsoft 25 .net, .net Framework, Visual Studio 2017 and 22 more 2024-05-29 N/A 7.8 HIGH
.NET and Visual Studio Remote Code Execution Vulnerability
CVE-2023-21567 1 Microsoft 3 Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 2024-05-29 N/A 5.6 MEDIUM
Visual Studio Denial of Service Vulnerability
CVE-2023-21566 1 Microsoft 3 Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 2024-05-29 N/A 7.8 HIGH
Visual Studio Elevation of Privilege Vulnerability
CVE-2023-36897 1 Microsoft 6 365 Apps, Office, Visual Studio 2010 Tools For Office Runtime and 3 more 2024-05-29 N/A 6.5 MEDIUM
Visual Studio Tools for Office Runtime Spoofing Vulnerability
CVE-2023-33139 1 Microsoft 4 Visual Studio, Visual Studio 2017, Visual Studio 2019 and 1 more 2024-05-29 N/A 5.5 MEDIUM
Visual Studio Information Disclosure Vulnerability
CVE-2023-28296 1 Microsoft 3 Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 2024-05-29 N/A 7.8 HIGH
Visual Studio Remote Code Execution Vulnerability
CVE-2023-24897 1 Microsoft 18 .net, .net Framework, Visual Studio and 15 more 2024-05-29 N/A 7.8 HIGH
.NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
CVE-2024-20656 1 Microsoft 4 Visual Studio, Visual Studio 2017, Visual Studio 2019 and 1 more 2024-05-29 N/A 7.8 HIGH
Visual Studio Elevation of Privilege Vulnerability
CVE-2020-1597 2 Fedoraproject, Microsoft 4 Fedora, Asp.net Core, Visual Studio 2017 and 1 more 2024-01-19 5.0 MEDIUM 7.5 HIGH
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests.
CVE-2020-1133 1 Microsoft 6 Visual Studio, Visual Studio 2017, Visual Studio 2019 and 3 more 2023-12-31 4.6 MEDIUM 5.5 MEDIUM
<p>An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector improperly handles file operations. An attacker who successfully exploited this vulnerability could run processes in an elevated context.</p> <p>An attacker could exploit this vulnerability by running a specially crafted application on the victim system.</p> <p>The update addresses the vulnerability by correcting the way the Diagnostics Hub Standard Collector handles file operations.</p>
CVE-2020-1130 1 Microsoft 6 Visual Studio, Visual Studio 2017, Visual Studio 2019 and 3 more 2023-12-31 4.6 MEDIUM 6.6 MEDIUM
<p>An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector improperly handles data operations. An attacker who successfully exploited this vulnerability could run processes in an elevated context.</p> <p>An attacker could exploit this vulnerability by running a specially crafted application on the victim system.</p> <p>The update addresses the vulnerability by correcting the way the Diagnostics Hub Standard Collector handles data operations.</p>
CVE-2020-16874 1 Microsoft 3 Visual Studio, Visual Studio 2017, Visual Studio 2019 2023-12-31 9.3 HIGH 7.8 HIGH
<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>