CVE-2018-1000058

Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin

Jenkins Pipeline: Supporting APIs Plugin 2.17 and earlier have an arbitrary code execution due to incomplete sandbox protection: Methods related to Java deserialization like readResolve implemented in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles.

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-2018-1000058 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 (2.18); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2018-1000058? CVE-2018-1000058 is a high-severity insecure deserialization vulnerability in org.jenkins-ci.plugins.workflow:workflow-support (maven), affecting versions <= 2.17. It is fixed in 2.18. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2018-1000058? CVE-2018-1000058 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.
3. Which versions of org.jenkins-ci.plugins.workflow:workflow-support are affected by CVE-2018-1000058? org.jenkins-ci.plugins.workflow:workflow-support (maven) versions <= 2.17 is affected.
4. Is there a fix for CVE-2018-1000058? Yes. CVE-2018-1000058 is fixed in 2.18. Upgrade to this version or later.
5. Is CVE-2018-1000058 exploitable, and should I be worried? Whether CVE-2018-1000058 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
6. What actually determines whether CVE-2018-1000058 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.
7. How do I fix CVE-2018-1000058? Upgrade org.jenkins-ci.plugins.workflow:workflow-support to 2.18 or later.

Other vulnerabilities in org.jenkins-ci.plugins.workflow:workflow-support