# CVE-2019-1351: Path traversal in Microsoft Visual Studio 2017

> An attacker can exploit improper virtual drive path handling in Git for Visual Studio to tamper with files and potentially execute code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-1351, CLEANSTART-2026-NJ16875, DEBIAN-CVE-2019-1351, GHSA-74x9-89m7-944x, UBUNTU-CVE-2019-1351

## What is CVE-2019-1351?

CVE-2019-1351 is a high-severity path traversal vulnerability in Microsoft Visual Studio 2017, published on 24 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

## Which versions are affected by CVE-2019-1351?

It affects 3 products.


Products: Microsoft Visual Studio 2017, Microsoft Visual Studio 2019, Opensuse Leap.

## How do I fix CVE-2019-1351?

Apply the vendor's patch.

## Is CVE-2019-1351 being exploited?

There is no known exploitation of CVE-2019-1351 in the wild and no public exploit code.

Public exploit code:

- Prueba de CVE-2019-1351 (github_poc): https://github.com/JonasDL/PruebaCVE20191351

## Other vulnerabilities in Microsoft Visual Studio 2017

- [CVE-2025-21178](https://insights.sbomify.com/CVE-2025-21178/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2019-1349](https://insights.sbomify.com/CVE-2019-1349/): Code injection in Microsoft Visual Studio 2017 (high 8.8)
- [CVE-2019-1350](https://insights.sbomify.com/CVE-2019-1350/): Code injection in Microsoft Visual Studio 2017 (high 8.8)
- [CVE-2019-1352](https://insights.sbomify.com/CVE-2019-1352/): Code injection in Microsoft Visual Studio 2017 (high 8.8)
- [CVE-2019-1354](https://insights.sbomify.com/CVE-2019-1354/): Code injection in Microsoft Visual Studio 2017 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1351 and fix it if it is affected.

What it is: CVE-2019-1351 is a high-severity path traversal vulnerability in Microsoft Visual Studio 2017, published on 24 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1351 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio 2017. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1351/ (Markdown: https://insights.sbomify.com/CVE-2019-1351/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1351
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1351
- OSV: https://osv.dev/vulnerability/CVE-2019-1351

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1351/
Summaries are generated and may contain mistakes; the official description above is the record.