What is CVE-2020-2213?

CVE-2020-2213 is a medium-severity security vulnerability in org.jenkins-ci.plugins:whitesource (maven), affecting versions < 20.8.1. It is fixed in 20.8.1.

How severe is CVE-2020-2213?

CVE-2020-2213 has a CVSS score of 4.3 (Medium). 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 org.jenkins-ci.plugins:whitesource are affected by CVE-2020-2213?

org.jenkins-ci.plugins:whitesource (maven) versions < 20.8.1 is affected.

Is there a fix for CVE-2020-2213?

Yes. CVE-2020-2213 is fixed in 20.8.1. Upgrade to this version or later.

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

Whether CVE-2020-2213 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-2213 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-2213 in org.jenkins-ci.plugins:whitesource

Q: How severe is CVE-2020-2213?

CVE-2020-2213 has a CVSS score of 4.3 (Medium). 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 org.jenkins-ci.plugins:whitesource are affected by CVE-2020-2213?

org.jenkins-ci.plugins:whitesource (maven) versions < 20.8.1 is affected.

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

Yes. CVE-2020-2213 is fixed in 20.8.1. Upgrade to this version or later.

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

Whether CVE-2020-2213 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-2213 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-2213?

Upgrade org.jenkins-ci.plugins:whitesource to 20.8.1 or later.

Summary

Credentials stored in plain text by Jenkins White Source Plugin

White Source Plugin prior to version 20.8.1 stores credentials in plain text as part of its global configuration file org.whitesource.jenkins.pipeline.WhiteSourcePipelineStep.xml and job config.xml files on the Jenkins controller. These credentials could be viewed by users with Extended Read permission (in the case of job config.xml files) or access to the Jenkins controller file system. Version 20.8.1 contains a patch for the issue.

Impact

CVE-2020-2213 has a CVSS score of 4.3 (Medium). 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 (20.8.1); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:whitesource (< 20.8.1)

Security releases

org.jenkins-ci.plugins:whitesource → 20.8.1 (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 org.jenkins-ci.plugins:whitesource to 20.8.1 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-2213? CVE-2020-2213 is a medium-severity security vulnerability in org.jenkins-ci.plugins:whitesource (maven), affecting versions < 20.8.1. It is fixed in 20.8.1.
How severe is CVE-2020-2213? CVE-2020-2213 has a CVSS score of 4.3 (Medium). 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 org.jenkins-ci.plugins:whitesource are affected by CVE-2020-2213? org.jenkins-ci.plugins:whitesource (maven) versions < 20.8.1 is affected.
Is there a fix for CVE-2020-2213? Yes. CVE-2020-2213 is fixed in 20.8.1. Upgrade to this version or later.
Is CVE-2020-2213 exploitable, and should I be worried? Whether CVE-2020-2213 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-2213 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-2213? Upgrade org.jenkins-ci.plugins:whitesource to 20.8.1 or later.