# CVE-2019-16565: Jenkins Team Concert Plugin cross-site request forgery vulnerability

> Attackers can exploit CSRF to force Jenkins to connect to malicious URLs, potentially capturing stored credentials.

- **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:** No
- **Published:** 17 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9h9v-rfh6-jf3w

## What is CVE-2019-16565?

CVE-2019-16565 is a high-severity vulnerability in Jenkins Team Concert Plugin, published on 17 Dec 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 request forgery vulnerability in Jenkins Team Concert Plugin 1.3.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:teamconcert. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:teamconcert` | Maven | All versions to 1.3.0 | None |
| `org.jenkins-ci.plugins:teamconcert` | Maven | All versions to 1.3.0 | None |

Products: Jenkins Team Concert.

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

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

## Is CVE-2019-16565 being exploited?

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

## Other vulnerabilities in Jenkins Team Concert Plugin

- [CVE-2019-16566](https://insights.sbomify.com/CVE-2019-16566/): Jenkins Team Concert Plugin missing permission check (medium 6.5)
- [CVE-2023-3315](https://insights.sbomify.com/CVE-2023-3315/): Jenkins Team Concert Plugin does not perform permission checks in methods implementing form validation (medium 4.3)
- [CVE-2019-16567](https://insights.sbomify.com/CVE-2019-16567/): Jenkins Team Concert Plugin missing permission check (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16565 is a high-severity vulnerability in Jenkins Team Concert Plugin, published on 17 Dec 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-16565 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:teamconcert (Maven): affected all versions up to 1.3.0; no fix listed
- org.jenkins-ci.plugins:teamconcert (Maven): affected all versions up to 1.3.0; 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-16565/ (Markdown: https://insights.sbomify.com/CVE-2019-16565/index.md)
```

## Sources

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

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