CVE-2020-2189 json
RCE vulnerability in SCM Filter Jervis Plugin
published 6y ago modified 4mo ago also GHSA-4hhq-j3xw-wj89 , EUVD-2022-2386
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven io.jenkins.plugins:scm-filter-jervis 0.3
Is CVE-2020-2189 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.28% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.jenkins.plugins:scm-filter-jervis | <0.3 |
0.3 |
Affected products
- Jenkins project Jenkins SCM Filter Jervis Plugin
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/jenkinsci/scm-filter-jervis-plugin/commit/a36e8bdef3a2a84737b64a898da4106793997273
web
-
jenkins.io
/security/advisory/2020-05-06/#SECURITY-1826
web, vendor-advisory
-
openwall.com
/lists/oss-security/2020/05/06/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-2189
advisory
-
github.com
/jenkinsci/scm-filter-jervis-plugin
package
Sources
- CVE List CVE-2020-2189
- GitHub Advisory GHSA-4hhq-j3xw-wj89
- NVD CVE-2020-2189
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.