# CVE-2020-2235: CSRF vulnerability in Jenkins Pipeline Maven Integration Plugin allow capturing credentials

> Attackers can exploit CSRF to connect to malicious JDBC URLs using stolen credentials, potentially capturing sensitive Jenkins credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** 12 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c2hg-2jj6-h8vh

## What is CVE-2020-2235?

CVE-2020-2235 is a medium-severity vulnerability in Jenkins Pipeline Maven Integration Plugin, published on 12 Aug 2020. 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 (CSRF) vulnerability in Jenkins Pipeline Maven Integration Plugin 3.8.2 and earlier allows attackers to connect to an attacker-specified JDBC URL using attacker-specified credentials IDs obtained through another method, potentially capturing credentials stored in Jenkins.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:pipeline-maven` | Maven | All versions | 3.8.3 |
| `org.jenkins-ci.plugins:pipeline-maven` | Maven | All versions | 3.8.3 |

Products: Jenkins Pipeline Maven Integration.

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

Upgrade org.jenkins-ci.plugins:pipeline-maven to 3.8.3 or later.

## Is CVE-2020-2235 being exploited?

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

## Other vulnerabilities in Jenkins Pipeline Maven Integration Plugin

- [CVE-2019-10327](https://insights.sbomify.com/CVE-2019-10327/): XML External Entity processing vulnerability in Pipeline Maven Integration Jenkins Plugin (high 8.1)
- [CVE-2020-2233](https://insights.sbomify.com/CVE-2020-2233/): Missing permission check in Jenkins Pipeline Maven Integration Plugin allows enumerating credentials IDs (medium 6.5)
- [CVE-2020-2234](https://insights.sbomify.com/CVE-2020-2234/): Missing permission check in Jenkins Pipeline Maven Integration Plugin allow capturing credentials (medium 6.5)
- [CVE-2020-2256](https://insights.sbomify.com/CVE-2020-2256/): Stored XSS vulnerability in Pipeline Maven Integration Plugin via unescaped display name (medium 5.4)
- [CVE-2023-41934](https://insights.sbomify.com/CVE-2023-41934/): Improper masking of credentials in Jenkins Pipeline Maven Integration Plugin (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2235 is a medium-severity vulnerability in Jenkins Pipeline Maven Integration Plugin, published on 12 Aug 2020. 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-2020-2235 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:pipeline-maven (Maven): affected all versions; fixed in 3.8.3
- org.jenkins-ci.plugins:pipeline-maven (Maven): affected all versions; fixed in 3.8.3

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

## Sources

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

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