CVE-2018-1000058: Workflow support Supporting APIs Plugin Vulnerability

HIGH
Advisory Identifier: GHSA-p3g4-9xfv-wq9v
Share
CVSS 8.8
CWE-502
Published
Advisory Summary

CVE-2018-1000058 is a HIGH (CVSS 8.8) supporting apis plugin vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Workflow support libraries in the Maven ecosystem. The issue involves supporting apis plugin. Remediation is available by upgrading affected packages to version 2.18.

CVE-2018-1000058 at a Glance

CVE Identifier CVE-2018-1000058
GHSA Identifier GHSA-p3g4-9xfv-wq9v
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product Workflow support
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2018-1000058

To remediate this vulnerability, upgrade all affected Workflow support dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.jenkins-ci.plugins.workflow:workflow-support fixed: 2.18 
<dependency>
    <groupId>org.jenkins-ci.plugins.workflow</groupId>
    <artifactId>workflow-support</artifactId>
    <version>2.18</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=org.jenkins-ci.plugins.workflow

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2018-1000058, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.jenkins-ci.plugins.workflow

Analyze the terminal output to locate any version of Workflow support in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.18), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.jenkins-ci.plugins.workflow command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Workflow support, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2018-1000058 Affected Workflow support Versions

1 component(s)
Fixed Versions:
2.18
Product / Package Ecosystem Affected Versions Fixed Version
org.jenkins-ci.plugins.workflow:workflow-support
maven/org.jenkins-ci.plugins.workflow/workflow-support
Maven
< 2.18
2.18

References

NVD — CVE-2018-1000058 NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-1000058
Workflow support Security Information SECURITY
https://jenkins.io/security/advisory/2018-02-05
Workflow support Security Information SECURITY
http://www.securityfocus.com/bid/103034

Frequently Asked Questions

What is CVE-2018-1000058?
CVE-2018-1000058 is a security vulnerability in Workflow support involving Supporting APIs Plugin under CWE-502: Deserialization of Untrusted Data.
Which Workflow support versions are affected?
Affected versions include releases prior to 2.18 across affected packages: org.jenkins-ci.plugins.workflow:workflow-support.
What version fixes CVE-2018-1000058?
Upgrading to 2.18 (or the latest patched release for your respective branch) resolves the vulnerability.
Is workflow-support affected?
Yes, org.jenkins-ci.plugins.workflow:workflow-support is affected in releases prior to 2.18. Upgrade your dependency to 2.18 or later.
What is the CVSS score of CVE-2018-1000058?
CVE-2018-1000058 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2018-1000058?
CVE-2018-1000058 is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check Maven dependencies for CVE-2018-1000058?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.jenkins-ci.plugins.workflow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p3g4-9xfv-wq9v",
  "modified" : "2024-01-30T23:18:21Z",
  "published" : "2022-05-14T03:40:05Z",
  "aliases" : [ "CVE-2018-1000058" ],
  "summary" : "Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.jenkins-ci.plugins.workflow:workflow-support"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.18"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.17"
    }
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-1000058"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2018-02-05"
  }, {
    "type" : "WEB",
    "url" : "http://www.securityfocus.com/bid/103034"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-01-30T23:18:21Z",
    "nvd_published_at" : "2018-02-09T23:29:00Z"
  }
}