Vulnerabilities in pkg:maven/org.jenkins-ci.plugins.workflow/workflow-support
PACKAGECVE-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.
pkg:maven/org.jenkins-ci.plugins.workflow/workflow-support
Vulnerability advisories affecting package pkg:maven/org.jenkins-ci.plugins.workflow/workflow-support. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-p3g4-9xfv-wq9v | CVE-2018-1000058 | HIGH | Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin |
| GHSA-64r9-x74q-wxmh | CVE-2022-43409 | HIGH | Stored XSS vulnerability in Jenkins Pipeline: Supporting APIs Plugin |
CVE-2018-1000058 at a Glance
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).
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.
<dependency>
<groupId>org.jenkins-ci.plugins.workflow</groupId>
<artifactId>workflow-support</artifactId>
<version>2.18</version>
</dependency>
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
CVE-2018-1000058 Affected Workflow support Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.jenkins-ci.plugins.workflow:workflow-support
|
Maven |
< 2.18
|
2.18
|
References
Frequently Asked Questions
What is CVE-2018-1000058?
Which Workflow support versions are affected?
What version fixes CVE-2018-1000058?
Is workflow-support affected?
What is the CVSS score of CVE-2018-1000058?
What CWE is associated with CVE-2018-1000058?
How can I check Maven dependencies for CVE-2018-1000058?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"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"
}
}