# CVE-2020-2196: Complete lack of CSRF protection in Jenkins Selenium Plugin can lead to OS command injection

> Attackers can perform administrative actions on the Jenkins Selenium Plugin due to missing CSRF protection, requiring an upgrade to secure the endpoints.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 3 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rp4x-xpgf-4xv7

## What is CVE-2020-2196?

CVE-2020-2196 is a high-severity vulnerability in Jenkins Selenium Plugin, published on 3 Jun 2020. 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 Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints, allowing attackers to perform all administrative actions provided by the plugin.

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

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

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


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

Products: Jenkins Selenium.

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

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

## Is CVE-2020-2196 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2196 and fix it if it is affected.

What it is: CVE-2020-2196 is a high-severity vulnerability in Jenkins Selenium Plugin, published on 3 Jun 2020. 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-2020-2196 in the wild and no public exploit code.

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

## Sources

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

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