# CVE-2022-25200: CSRF vulnerability in Jenkins Checkmarx Plugin allow capturing credentials

> Attackers can exploit CSRF to connect Jenkins to a malicious server, capturing stored credentials via attacker-specified IDs.

- **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:** Yes
- **Published:** 15 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5pcf-vxm3-frph

## What is CVE-2022-25200?

CVE-2022-25200 is a high-severity vulnerability in Jenkins Checkmarx Plugin, published on 15 Feb 2022. 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 Checkmarx Plugin 2022.1.2 and earlier allows attackers to connect to an attacker-specified webserver 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-2022-25200?

2 open source packages ship an affected version, including com.checkmarx.jenkins:checkmarx. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.checkmarx.jenkins:checkmarx` | Maven | All versions | 2022.1.3 |
| `com.checkmarx.jenkins:checkmarx` | Maven | All versions | 2022.1.3 |

Products: Jenkins Checkmarx.

## How do I fix CVE-2022-25200?

Upgrade com.checkmarx.jenkins:checkmarx to 2022.1.3 or later.

## Is CVE-2022-25200 being exploited?

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

## Other vulnerabilities in Jenkins Checkmarx Plugin

- [CVE-2023-35142](https://insights.sbomify.com/CVE-2023-35142/): SSL/TLS certificate validation disabled by default in Jenkins Checkmarx Plugin (high 8.1)
- [CVE-2022-25201](https://insights.sbomify.com/CVE-2022-25201/): Missing permission checks in Jenkins Checkmarx Plugin allow capturing credentials (medium 6.5)
- [CVE-2022-46684](https://insights.sbomify.com/CVE-2022-46684/): Stored XSS vulnerability in Jenkins Checkmarx Plugin (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25200 and fix it if it is affected.

What it is: CVE-2022-25200 is a high-severity vulnerability in Jenkins Checkmarx Plugin, published on 15 Feb 2022. 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-2022-25200 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.checkmarx.jenkins:checkmarx (Maven): affected all versions; fixed in 2022.1.3
- com.checkmarx.jenkins:checkmarx (Maven): affected all versions; fixed in 2022.1.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-2022-25200/ (Markdown: https://insights.sbomify.com/CVE-2022-25200/index.md)
```

## Sources

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

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