Vulnerabilities > Microsoft > Visual Studio 2019 > High
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2020-06-09 | CVE-2020-1202 | Improper Privilege Management vulnerability in Microsoft products An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector fail to properly handle objects in memory, aka 'Diagnostic Hub Standard Collector Elevation of Privilege Vulnerability'. | 7.2 |
2020-05-21 | CVE-2020-1108 | Unspecified vulnerability in Microsoft products A denial of service vulnerability exists when .NET Core or .NET Framework improperly handles web requests, aka '.NET Core & .NET Framework Denial of Service Vulnerability'. | 7.5 |
2020-03-12 | CVE-2020-0810 | Improper Privilege Management vulnerability in Microsoft products An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector allows file creation in arbitrary locations.To exploit the vulnerability, an attacker would first have to log on to the system.An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system.The update addresses the vulnerability by not permitting Diagnostics Hub Standard Collector or the Visual Studio Standard Collector to create files in arbitrary locations., aka 'Diagnostic Hub Standard Collector Elevation of Privilege Vulnerability'. | 7.2 |
2020-01-24 | CVE-2019-1354 | Improper Input Validation vulnerability in Microsoft Visual Studio 2017 A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. | 8.8 |
2020-01-24 | CVE-2019-1352 | Improper Input Validation vulnerability in Microsoft Visual Studio 2017 A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. | 8.8 |
2020-01-24 | CVE-2019-1351 | Use of Incorrectly-Resolved Name or Reference vulnerability in multiple products A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'. | 7.5 |
2020-01-24 | CVE-2019-1350 | Improper Input Validation vulnerability in Microsoft Visual Studio 2017 A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. | 8.8 |
2020-01-24 | CVE-2019-1349 | Improper Input Validation vulnerability in Microsoft Visual Studio 2017 A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. | 8.8 |
2019-08-14 | CVE-2019-1211 | Unspecified vulnerability in Microsoft Visual Studio 2017 and Visual Studio 2019 An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. | 7.3 |
2019-05-16 | CVE-2019-0727 | Unspecified vulnerability in Microsoft products An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector allows file deletion in arbitrary locations.To exploit the vulnerability, an attacker would first have to log on to the system, aka 'Diagnostic Hub Standard Collector, Visual Studio Standard Collector Elevation of Privilege Vulnerability'. | 7.2 |