# CVE-2022-28137: Missing permission check in Jenkins JiraTestResultReporter Plugin

> Attackers with Overall/Read permission can bypass authorization to connect to arbitrary URLs using specified credentials in the Jenkins JiraTestResultReporter Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gc7m-x2cj-3775

## What is CVE-2022-28137?

CVE-2022-28137 is a medium-severity missing authorization vulnerability in Jenkins JiraTestResultReporter Plugin, published on 29 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins JiraTestResultReporter Plugin 165.v817928553942 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:JiraTestResultReporter` | Maven | All versions | 166.v0cc6208295b5 |
| `org.jenkins-ci.plugins:JiraTestResultReporter` | Maven | All versions | 166.v0cc6208295b5 |

Products: Jenkins Jiratestresultreporter.

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

Upgrade org.jenkins-ci.plugins:JiraTestResultReporter to 166.v0cc6208295b5 or later.

## Is CVE-2022-28137 being exploited?

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

## Other vulnerabilities in Jenkins JiraTestResultReporter Plugin

- [CVE-2022-28136](https://insights.sbomify.com/CVE-2022-28136/): CSRF vulnerability and missing permission check in Jenkins JiraTestResultReporter Plugin (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28137 is a medium-severity missing authorization vulnerability in Jenkins JiraTestResultReporter Plugin, published on 29 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28137 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:JiraTestResultReporter (Maven): affected all versions; fixed in 166.v0cc6208295b5
- org.jenkins-ci.plugins:JiraTestResultReporter (Maven): affected all versions; fixed in 166.v0cc6208295b5

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

## Sources

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

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