# CVE-2022-36887: Jenkins Job Configuration History Plugin does not require POST requests for several HTTP endpoints

> Attackers can delete or restore configuration history entries in Jenkins via CSRF, requiring plugin updates to mitigate.

- **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:** 27 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j896-j72w-cr32

## What is CVE-2022-36887?

CVE-2022-36887 is a medium-severity vulnerability in Jenkins Job Configuration History Plugin, published on 27 Jul 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 Job Configuration History Plugin 1155.v28a_46a_cc06a_5 and earlier allows attackers to delete entries from job, agent, and system configuration history, or restore older versions of job, agent, and system configurations.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1156.v536a_97b_8d649 |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1156.v536a_97b_8d649 |

Products: Jenkins Job Configuration History.

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

Upgrade org.jenkins-ci.plugins:jobConfigHistory to 1156.v536a_97b_8d649 or later.

## Is CVE-2022-36887 being exploited?

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

## Other vulnerabilities in Jenkins Job Configuration History Plugin

- [CVE-2023-41933](https://insights.sbomify.com/CVE-2023-41933/): Job Configuration History Plugin's path traversal allows exploiting XXE vulnerability (high 8.8)
- [CVE-2023-41932](https://insights.sbomify.com/CVE-2023-41932/): Path traversal allows exploiting XXE vulnerability in Jenkins Job Configuration History Plugin (medium 6.5)
- [CVE-2023-41931](https://insights.sbomify.com/CVE-2023-41931/): XSS vulnerability in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2022-38664](https://insights.sbomify.com/CVE-2022-38664/): Cross-site Scripting in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2026-57287](https://insights.sbomify.com/CVE-2026-57287/): Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36887 is a medium-severity vulnerability in Jenkins Job Configuration History Plugin, published on 27 Jul 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-36887 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1156.v536a_97b_8d649
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1156.v536a_97b_8d649

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

## Sources

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

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