Microsoft Visual Studio 2019 16.2
Approved changes feed: RSS · Atom
cpe:2.3:a:microsoft:visual_studio_2019:16.2:*:*:*:*:*:*:*
part: a version: 16.2 update: *
| Vendor | Microsoft (67206627-3ef6-5870-9d98-26a9f2e7065c) |
|---|---|
| Product | Visual Studio 2019 (10a9a1d0-3f4a-5e5c-8b94-2e33544bd838) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-1232 |
vulnerable | 2026-06-08 05:13:25.356208 |
Details available
An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly impersonates certain file operations, aka 'Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability'.
Published: 2019-09-11T21:24:58.000Z
Updated: 2024-08-04T18:13:29.614Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-1211 |
vulnerable | 2026-06-08 05:13:25.286066 |
Git for Visual Studio Elevation of Privilege Vulnerability
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.
Published: 2019-08-14T20:55:05.000Z
Updated: 2024-08-04T18:13:29.223Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.