# CVE-2019-0867: Cross-site scripting in Azure DevOps Server

> Attackers can execute arbitrary scripts in user browsers via unsanitized input in Azure DevOps Server and Team Foundation Server.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** No
- **Published:** 9 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2cf6-m3mv-f2w7

## What is CVE-2019-0867?

CVE-2019-0867 is a medium-severity cross-site scripting vulnerability in Microsoft Azure DevOps Server, published on 9 Apr 2019. 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 Cross-site Scripting (XSS) vulnerability exists when Azure DevOps Server and Team Foundation Server do not properly sanitize user provided input, aka 'Azure DevOps Server and Team Foundation Server Cross-site Scripting Vulnerability'. This CVE ID is unique from CVE-2019-0866, CVE-2019-0868, CVE-2019-0870, CVE-2019-0871.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 2 products.


Products: Microsoft Azure Devops Server, Microsoft Team Foundation Server.

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

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

## Is CVE-2019-0867 being exploited?

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

## Other vulnerabilities in Microsoft Azure DevOps Server

- [CVE-2019-1306](https://insights.sbomify.com/CVE-2019-1306/): Code injection in Azure DevOps Server (critical 9.8)
- [CVE-2019-1072](https://insights.sbomify.com/CVE-2019-1072/): Code injection in Azure DevOps Server (critical 9.8)
- [CVE-2023-33136](https://insights.sbomify.com/CVE-2023-33136/): Azure DevOps Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-35266](https://insights.sbomify.com/CVE-2024-35266/): Azure DevOps Server Spoofing Vulnerability (high 7.6)
- [CVE-2024-35267](https://insights.sbomify.com/CVE-2024-35267/): Azure DevOps Server Spoofing Vulnerability (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0867 is a medium-severity cross-site scripting vulnerability in Microsoft Azure DevOps Server, published on 9 Apr 2019. 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-0867 in the wild and no public exploit code.

Affected product: Microsoft Azure DevOps Server. 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-0867/ (Markdown: https://insights.sbomify.com/CVE-2019-0867/index.md)
```

## Sources

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

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