# CVE-2020-2189: RCE vulnerability in SCM Filter Jervis Plugin

> Remote attackers can execute arbitrary code on Jenkins servers via unsafe YAML deserialization in the SCM Filter Jervis 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:** Yes
- **Published:** 6 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4hhq-j3xw-wj89

## What is CVE-2020-2189?

CVE-2020-2189 is a high-severity unsafe deserialization vulnerability in Jenkins SCM Filter Jervis Plugin, published on 6 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins SCM Filter Jervis Plugin 0.2.1 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-2189?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:scm-filter-jervis` | Maven | All versions | 0.3 |
| `io.jenkins.plugins:scm-filter-jervis` | Maven | All versions | 0.3 |

Products: Jenkins Source Code Management Filter Jervis.

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

Upgrade io.jenkins.plugins:scm-filter-jervis to 0.3 or later.

## Is CVE-2020-2189 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2189 is a high-severity unsafe deserialization vulnerability in Jenkins SCM Filter Jervis Plugin, published on 6 May 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-2189 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:scm-filter-jervis (Maven): affected all versions; fixed in 0.3
- io.jenkins.plugins:scm-filter-jervis (Maven): affected all versions; fixed in 0.3

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

## Sources

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

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