# CVE-2019-16563: Cross site scripting in Jenkins Mission Control Plugin

> Stored XSS in Jenkins Mission Control Plugin allows attackers to execute scripts via unescaped job or build names, potentially leading to session hijacking.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9523-474x-5h36

## What is CVE-2019-16563?

CVE-2019-16563 is a medium-severity cross-site scripting vulnerability in Jenkins Mission Control Plugin, published on 17 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jenkins Mission Control Plugin 0.9.16 and earlier does not escape job display names and build names shown on its view, resulting in a stored XSS vulnerability exploitable by attackers able to change these properties.

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

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

2 open source packages ship an affected version, including tech.andrey.jenkins:mission-control-view. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tech.andrey.jenkins:mission-control-view` | Maven | All versions to 0.9.16 | None |
| `tech.andrey.jenkins:mission-control-view` | Maven | All versions to 0.9.16 | None |

Products: Jenkins Mission Control.

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

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

## Is CVE-2019-16563 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16563 is a medium-severity cross-site scripting vulnerability in Jenkins Mission Control Plugin, published on 17 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-16563 in the wild and no public exploit code.

Affected packages and fixed versions:
- tech.andrey.jenkins:mission-control-view (Maven): affected all versions up to 0.9.16; no fix listed
- tech.andrey.jenkins:mission-control-view (Maven): affected all versions up to 0.9.16; no fix listed

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-16563/ (Markdown: https://insights.sbomify.com/CVE-2019-16563/index.md)
```

## Sources

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

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