Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Visual_studio_2019
(Microsoft)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 99 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2024-10-08 | CVE-2024-43603 | Visual Studio Collector Service Denial of Service Vulnerability | Visual_studio, Visual_studio_2017, Visual_studio_2019, Visual_studio_2022 | 5.5 | ||
2024-10-08 | CVE-2024-43590 | Visual C++ Redistributable Installer Elevation of Privilege Vulnerability | Visual_studio_2017, Visual_studio_2019, Visual_studio_2022 | 7.8 | ||
2019-08-14 | CVE-2019-1211 | 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... | Visual_studio_2017, Visual_studio_2019 | 7.3 | ||
2020-01-24 | CVE-2019-1349 | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387. | Visual_studio_2017, Visual_studio_2019 | 8.8 | ||
2020-01-24 | CVE-2019-1350 | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387. | Visual_studio_2017, Visual_studio_2019 | 8.8 | ||
2020-01-24 | CVE-2019-1351 | A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'. | Visual_studio_2017, Visual_studio_2019, Leap | 7.5 | ||
2020-01-24 | CVE-2019-1352 | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387. | Visual_studio_2017, Visual_studio_2019 | 8.8 | ||
2020-01-24 | CVE-2019-1354 | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1352, CVE-2019-1387. | Visual_studio_2017, Visual_studio_2019 | 8.8 | ||
2020-03-12 | CVE-2020-0793 | An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles file operations, aka 'Diagnostics Hub Standard Collector Elevation of Privilege Vulnerability'. | Visual_studio_2015, Visual_studio_2017, Visual_studio_2019, Windows_10, Windows_server_2016, Windows_server_2019 | 7.8 | ||
2020-03-12 | CVE-2020-0810 | 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_2015, Visual_studio_2017, Visual_studio_2019, Windows_10, Windows_server_2016, Windows_server_2019 | 7.8 |