# CVE-2021-21613: XSS vulnerability in Jenkins TICS Plugin

> Attackers controlling TICS service responses can inject malicious scripts into Jenkins, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** Yes
- **Published:** 13 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xmw5-45v9-pxqx

## What is CVE-2021-21613?

CVE-2021-21613 is a medium-severity cross-site scripting vulnerability in Jenkins TICS Plugin, published on 13 Jan 2021. 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

Jenkins TICS Plugin 2020.3.0.6 and earlier does not escape TICS service responses, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers able to control TICS service response content.

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

## Which versions are affected by CVE-2021-21613?

2 open source packages ship an affected version, including io.jenkins.plugins:tics. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:tics` | Maven | All versions | 2020.3.0.7 |
| `io.jenkins.plugins:tics` | Maven | All versions | 2020.3.0.7 |

Products: Jenkins Tics.

## How do I fix CVE-2021-21613?

Upgrade io.jenkins.plugins:tics to 2020.3.0.7 or later.

## Is CVE-2021-21613 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-21613 and fix it if it is affected.

What it is: CVE-2021-21613 is a medium-severity cross-site scripting vulnerability in Jenkins TICS Plugin, published on 13 Jan 2021. 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-2021-21613 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:tics (Maven): affected all versions; fixed in 2020.3.0.7
- io.jenkins.plugins:tics (Maven): affected all versions; fixed in 2020.3.0.7

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

## Sources

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

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