# CVE-2020-2211: RCE vulnerability in ElasticBox Jenkins Kubernetes CI/CD Plugin

> Attackers can achieve remote code execution via unsafe YAML deserialization in the Jenkins ElasticBox Kubernetes CI/CD Plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9r3h-wm3x-v245

## What is CVE-2020-2211?

CVE-2020-2211 is a high-severity unsafe deserialization vulnerability in Jenkins ElasticBox Jenkins Kubernetes CI/CD Plugin, published on 2 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins ElasticBox Jenkins Kubernetes CI/CD Plugin 1.3 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.elasticbox.jenkins-ci.plugins:kubernetes-ci` | Maven | All versions to 1.3 | None |
| `com.elasticbox.jenkins-ci.plugins:kubernetes-ci` | Maven | All versions to 1.3 | None |

Products: Jenkins Kubernetes Ci.

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

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

## Is CVE-2020-2211 being exploited?

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

## Other vulnerabilities in Jenkins ElasticBox Jenkins Kubernetes CI/CD Plugin

- [CVE-2019-10468](https://insights.sbomify.com/CVE-2019-10468/): Jenkins Kubernetes CI/CD Plugin vulnerable to Cross-Site Request Forgery (high 8.8)
- [CVE-2019-10469](https://insights.sbomify.com/CVE-2019-10469/): Jenkins Kubernetes CI/CD Plugin vulnerable to Improper Authorization (medium 6.5)
- [CVE-2019-10470](https://insights.sbomify.com/CVE-2019-10470/): Jenkins Kubernetes CI/CD Plugin vulnerable to Credential Enumeration (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2211 is a high-severity unsafe deserialization vulnerability in Jenkins ElasticBox Jenkins Kubernetes CI/CD Plugin, published on 2 Jul 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-2211 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.elasticbox.jenkins-ci.plugins:kubernetes-ci (Maven): affected all versions up to 1.3; no fix listed
- com.elasticbox.jenkins-ci.plugins:kubernetes-ci (Maven): affected all versions up to 1.3; 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-2211/ (Markdown: https://insights.sbomify.com/CVE-2020-2211/index.md)
```

## Sources

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

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