# CVE-2019-1352: Code injection in Microsoft Visual Studio 2017

> Attackers can execute arbitrary code via improper input sanitization in Git for Visual Studio, affecting developers using this tool.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-1352, CLEANSTART-2025-CH00091, DEBIAN-CVE-2019-1352, GHSA-74fq-3g57-65f7, UBUNTU-CVE-2019-1352

## What is CVE-2019-1352?

CVE-2019-1352 is a high-severity code injection vulnerability in Microsoft Visual Studio 2017, published on 24 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


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

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

Apply the vendor's patch.

## Is CVE-2019-1352 being exploited?

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

## 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-1354](https://insights.sbomify.com/CVE-2019-1354/): Code injection in Microsoft Visual Studio 2017 (high 8.8)
- [CVE-2023-28296](https://insights.sbomify.com/CVE-2023-28296/): Visual Studio Remote Code Execution Vulnerability (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1352 is a high-severity code injection vulnerability in Microsoft Visual Studio 2017, published on 24 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1352 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-1352/ (Markdown: https://insights.sbomify.com/CVE-2019-1352/index.md)
```

## Sources

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

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