What is CVE-2020-2189?

CVE-2020-2189 is a high-severity insecure deserialization vulnerability in io.jenkins.plugins:scm-filter-jervis (maven), affecting versions <= 0.2.1. It is fixed in 0.3. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2020-2189?

CVE-2020-2189 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of io.jenkins.plugins:scm-filter-jervis are affected by CVE-2020-2189?

io.jenkins.plugins:scm-filter-jervis (maven) versions <= 0.2.1 is affected.

Is there a fix for CVE-2020-2189?

Yes. CVE-2020-2189 is fixed in 0.3. Upgrade to this version or later.

Is CVE-2020-2189 exploitable, and should I be worried?

Whether CVE-2020-2189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-2189 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2020-2189

Q: How severe is CVE-2020-2189?

CVE-2020-2189 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of io.jenkins.plugins:scm-filter-jervis are affected by CVE-2020-2189?

io.jenkins.plugins:scm-filter-jervis (maven) versions <= 0.2.1 is affected.

Q: Is there a fix for CVE-2020-2189?

Yes. CVE-2020-2189 is fixed in 0.3. Upgrade to this version or later.

Q: Is CVE-2020-2189 exploitable, and should I be worried?

Whether CVE-2020-2189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-2189 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-2189?

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

Summary

RCE vulnerability in SCM Filter Jervis Plugin

SCM Filter Jervis Plugin 0.2.1 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types. This results in a remote code execution (RCE) vulnerability exploitable by users able to configure jobs with the filter, or control the contents of a previously configured job’s SCM repository.

SCM Filter Jervis Plugin 0.3 configures its YAML parser to only instantiate safe types.

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2020-2189 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.3); upgrading removes the vulnerable code path.

Affected versions

io.jenkins.plugins:scm-filter-jervis (<= 0.2.1)

Security releases

io.jenkins.plugins:scm-filter-jervis → 0.3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-2189? CVE-2020-2189 is a high-severity insecure deserialization vulnerability in io.jenkins.plugins:scm-filter-jervis (maven), affecting versions <= 0.2.1. It is fixed in 0.3. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2020-2189? CVE-2020-2189 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of io.jenkins.plugins:scm-filter-jervis are affected by CVE-2020-2189? io.jenkins.plugins:scm-filter-jervis (maven) versions <= 0.2.1 is affected.
Is there a fix for CVE-2020-2189? Yes. CVE-2020-2189 is fixed in 0.3. Upgrade to this version or later.
Is CVE-2020-2189 exploitable, and should I be worried? Whether CVE-2020-2189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-2189 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-2189? Upgrade io.jenkins.plugins:scm-filter-jervis to 0.3 or later.