# CVE-2022-36890: Jenkins Deployer Framework Plugin vulnerable to Path Traversal

> Attackers with Item/Read permission can check for the existence of arbitrary files on the Jenkins controller file system via the Deployer Framework Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 27 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hgp9-2c4w-x9mh

## What is CVE-2022-36890?

CVE-2022-36890 is a medium-severity path traversal vulnerability in Jenkins Deployer Framework Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Deployer Framework Plugin 85.v1d1888e8c021 and earlier does not restrict the name of files in methods implementing form validation, allowing attackers with Item/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:deployer-framework` | Maven | All versions | 86.v7b_a_4a_55b_f3ec |
| `org.jenkins-ci.plugins:deployer-framework` | Maven | All versions | 86.v7b_a_4a_55b_f3ec |

Products: Jenkins Deployer Framework.

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

Upgrade org.jenkins-ci.plugins:deployer-framework to 86.v7b_a_4a_55b_f3ec or later.

## Is CVE-2022-36890 being exploited?

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

## Other vulnerabilities in Jenkins Deployer Framework Plugin

- [CVE-2022-36889](https://insights.sbomify.com/CVE-2022-36889/): Jenkins Deployer Framework Plugin does not restrict application path of applications when configuring a deployment (high 8.8)
- [CVE-2020-2227](https://insights.sbomify.com/CVE-2020-2227/): Stored XSS vulnerability in Jenkins Deployer Framework Plugin (medium 5.4)
- [CVE-2022-36891](https://insights.sbomify.com/CVE-2022-36891/): Jenkins Deployer Framework Plugin allows attackers with Item/Read permission to read deployment logs (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36890 is a medium-severity path traversal vulnerability in Jenkins Deployer Framework Plugin, published on 27 Jul 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-36890 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:deployer-framework (Maven): affected all versions; fixed in 86.v7b_a_4a_55b_f3ec
- org.jenkins-ci.plugins:deployer-framework (Maven): affected all versions; fixed in 86.v7b_a_4a_55b_f3ec

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

## Sources

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

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