# CVE-2020-2322: Missing permission checks in Jenkins Chaos Monkey Plugin

> Attackers with read permissions can cause denial of service by generating load and memory leaks due to missing permission checks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mr75-899x-qcxq

## What is CVE-2020-2322?

CVE-2020-2322 is a high-severity missing authorization vulnerability in Jenkins Chaos Monkey Plugin, published on 3 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Chaos Monkey Plugin 0.3 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to generate load and to generate memory leaks.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-2322?

2 open source packages ship an affected version, including io.jenkins.plugins:chaos-monkey. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:chaos-monkey` | Maven | All versions | 0.4 |
| `io.jenkins.plugins:chaos-monkey` | Maven | All versions | 0.4 |

Products: Netflix Chaos Monkey.

## How do I fix CVE-2020-2322?

Upgrade io.jenkins.plugins:chaos-monkey to 0.4 or later.

## Is CVE-2020-2322 being exploited?

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

## Other vulnerabilities in Jenkins Chaos Monkey Plugin

- [CVE-2020-2323](https://insights.sbomify.com/CVE-2020-2323/): Missing permission checks in Jenkins Chaos Monkey Plugin (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2322 and fix it if it is affected.

What it is: CVE-2020-2322 is a high-severity missing authorization vulnerability in Jenkins Chaos Monkey Plugin, published on 3 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2322 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:chaos-monkey (Maven): affected all versions; fixed in 0.4
- io.jenkins.plugins:chaos-monkey (Maven): affected all versions; fixed in 0.4

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

## Sources

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

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