# CVE-2022-20613: Cross-Site Request Forgery in Jenkins Mailer Plugin

> Attackers can exploit CSRF to force Jenkins to resolve attacker-specified hostnames using the instance's DNS configuration.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 12 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-85rq-hp8x-ghjq

## What is CVE-2022-20613?

CVE-2022-20613 is a medium-severity vulnerability in Oracle Communications Cloud Native Core Automated Test Suite, published on 12 Jan 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 Mailer Plugin 391.ve4a_38c1b_cf4b_ and earlier allows attackers to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname.

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

## Which versions are affected by CVE-2022-20613?

4 open source packages ship an affected version, including org.jenkins-ci.plugins:mailer. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:mailer` | Maven | All versions | 1.34.2 |
| `org.jenkins-ci.plugins:mailer` | Maven | All versions | 1.34.2 |
| `org.jenkins-ci.plugins:mailer` | Maven | From 391.ve4a38c1bcf4b | 408.vd726a |
| `org.jenkins-ci.plugins:mailer` | Maven | From 391.ve4a38c1bcf4b | 408.vd726a |

Products: Jenkins Mailer, Oracle Communications Cloud Native Core Automated Test Suite.

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

Upgrade org.jenkins-ci.plugins:mailer to a fixed version for your release line: 1.34.2 or 408.vd726a.

## Is CVE-2022-20613 being exploited?

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

## Other vulnerabilities in Oracle Communications Cloud Native Core Automated Test Suite

- [CVE-2018-8718](https://insights.sbomify.com/CVE-2018-8718/): Cross-Site Request Forgery in Jenkins Mailer Plugin (high 8.0)
- [CVE-2020-2252](https://insights.sbomify.com/CVE-2020-2252/): Improper Validation of Certificate with Host Mismatch in Jenkins Mailer Plugin (medium 4.8)
- [CVE-2022-20614](https://insights.sbomify.com/CVE-2022-20614/): Incorrect Permission Assignment for Critical Resource in Jenkins Mailer Plugin (medium 4.3)
- [CVE-2017-2651](https://insights.sbomify.com/CVE-2017-2651/): Exposure of Sensitive Information to an Unauthorized Actor in Jenkins-mailer-plugin (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-20613 is a medium-severity vulnerability in Oracle Communications Cloud Native Core Automated Test Suite, published on 12 Jan 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-20613 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:mailer (Maven): affected all versions; fixed in 1.34.2
- org.jenkins-ci.plugins:mailer (Maven): affected all versions; fixed in 1.34.2
- org.jenkins-ci.plugins:mailer (Maven): affected from 391.ve4a38c1bcf4b; fixed in 408.vd726a
- org.jenkins-ci.plugins:mailer (Maven): affected from 391.ve4a38c1bcf4b; fixed in 408.vd726a

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

## Sources

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

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