CVE Vulnerabilities for Visual Studio 2019
| CVE | Published | Severity | Details | Exploitability | Impact | Vector |
|---|---|---|---|---|---|---|
| CVE‑2022‑24767 | 2022‑04‑12 18:15:10 | HIGH (8) | GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account. | 2 | 6 | LOCAL |
| CVE‑2022‑21871 | 2022‑01‑11 21:15:11 | HIGH (8) | Microsoft Diagnostics Hub Standard Collector Runtime Elevation of Privilege Vulnerability | 2 | 6 | LOCAL |
| CVE‑2020‑1147 | 2020‑07‑14 23:15:12 | HIGH (8) | A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check the source markup of XML file input, aka '.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability'. | 2 | 6 | LOCAL |
| CVE‑2020‑0899 | 2020‑04‑15 15:15:14 | MEDIUM (6) | An elevation of privilege vulnerability exists when Microsoft Visual Studio updater service improperly handles file permissions, aka 'Microsoft Visual Studio Elevation of Privilege Vulnerability'. | 2 | 4 | LOCAL |
| CVE‑2020‑0884 | 2020‑03‑12 16:15:20 | LOW (4) | A spoofing vulnerability exists in Microsoft Visual Studio as it includes a reply URL that is not secured by SSL, aka 'Microsoft Visual Studio Spoofing Vulnerability'. | 2 | 1 | NETWORK |
| CVE‑2019‑1354 | 2020‑01‑24 21:15:13 | HIGH (9) | 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. | 3 | 6 | NETWORK |
| CVE‑2019‑1352 | 2020‑01‑24 21:15:13 | HIGH (9) | 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. | 3 | 6 | NETWORK |
| CVE‑2019‑1351 | 2020‑01‑24 21:15:13 | HIGH (8) | A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'. | 4 | 4 | NETWORK |
| CVE‑2019‑1350 | 2020‑01‑24 21:15:13 | HIGH (9) | 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. | 3 | 6 | NETWORK |
| CVE‑2019‑1349 | 2020‑01‑24 21:15:13 | HIGH (9) | 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. | 3 | 6 | NETWORK |
| CVE‑2019‑1211 | 2019‑08‑14 21:15:18 | LOW (4) | 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. | 0 | 0 | LOCAL |
View OS-specific patching for:
Windows Mac Linux
Logos, products, trade names, and company names are all the property of their respective trademark holders.
The above listing includes products that Lavawall® monitors through public information and/or proprietary statistical analysis.
Although we do have a partner relationship with some of the listed products and companies, they do not necessarily endorse Lavawall® or have integrations with our systems.