Visual Studio
CVE-2019-1211 — Git for Visual Studio Elevation of Privilege Vulnerability
Executive Summary
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.
Overview
7.3
CVSS HIGH
Important
MS Severity
Not Exploited
MS Exploit Status
Less Likely
MS Exploit Likelihood
CVSS Vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
ATTACK VECTOR
Local
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
Low
USER INTERACTION
Required
SCOPE
Unchanged
EPSS Score
0.01654
probability of exploitation in the next 30 days
0.74139 percentile - updated 2026-07-25
View on FIRST.org
Affected Products
4 affected products
| Product | KB Article | Severity | Impact | Restart Required |
|---|---|---|---|---|
| Microsoft Visual Studio 2017 | Release Notes (Security Update) |
Important | Elevation of Privilege | Maybe |
| Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) | Release Notes (Security Update) |
Important | Elevation of Privilege | Maybe |
| Microsoft Visual Studio 2019 version 16.0 | Release Notes (Security Update) |
Important | Elevation of Privilege | Maybe |
| Microsoft Visual Studio 2019 version 16.2 | Release Notes (Security Update) |
Important | Elevation of Privilege | Maybe |
Patches
1 patch
| Article | Type | Restart |
|---|---|---|
Release Notes |
Security Update | Maybe |
Known Exploits
No known exploits have been linked for this CVE yet. When available, exploit references will be sourced from public repositories and may be unverified, incomplete, or non-functional. Always review code carefully before use in any environment.
Acknowledgments
References
On This Page