# CVE-2020-0884: Other in Microsoft Visual Studio 2017 version 15.9 (includes 15.1 - 15.8)

> An attacker can spoof responses in Microsoft Visual Studio due to an unsecured reply URL, potentially bypassing security controls.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qhw6-g646-98wf

## What is CVE-2020-0884?

CVE-2020-0884 is a low-severity vulnerability in Microsoft Visual Studio 2017, published on 12 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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'.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2020-0884?

It affects 2 products.


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

## How do I fix CVE-2020-0884?

No fix has been published for CVE-2020-0884 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-0884 being exploited?

There is no known exploitation of CVE-2020-0884 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-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-2020-0884 and fix it if it is affected.

What it is: CVE-2020-0884 is a low-severity vulnerability in Microsoft Visual Studio 2017, published on 12 Mar 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-2020-0884 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-2020-0884/ (Markdown: https://insights.sbomify.com/CVE-2020-0884/index.md)
```

## Sources

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

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