# CVE-2020-2272: Missing permission checks in Jenkins ElasTest Plugin

> Attackers with read permissions can bypass authorization to connect to arbitrary URLs using specified credentials in the Jenkins ElasTest 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:** No
- **Published:** 16 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mr43-vf8q-q5f2

## What is CVE-2020-2272?

CVE-2020-2272 is a medium-severity missing authorization vulnerability in Jenkins ElasTest Plugin, published on 16 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins ElasTest Plugin 1.2.1 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-2020-2272?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:elastest` | Maven | All versions to 1.2.1 | None |
| `org.jenkins-ci.plugins:elastest` | Maven | All versions to 1.2.1 | None |

Products: Jenkins Elastest.

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

No fix has been published for CVE-2020-2272 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-2272 being exploited?

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

## Other vulnerabilities in Jenkins ElasTest Plugin

- [CVE-2020-2274](https://insights.sbomify.com/CVE-2020-2274/): Passwords stored in plain text by ElasTest Plugin (medium 5.5)
- [CVE-2020-2273](https://insights.sbomify.com/CVE-2020-2273/): CSRF vulnerability in Jenkins ElasTest Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- org.jenkins-ci.plugins:elastest (Maven): affected all versions up to 1.2.1; no fix listed
- org.jenkins-ci.plugins:elastest (Maven): affected all versions up to 1.2.1; no fix listed

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

## Sources

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

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