CVE-2018-1000015 — workflow-durable-task-step
MEDIUMCVE-2018-1000015 is a medium-severity (CVSS 4.8) CWE-862 vulnerability in org.jenkins-ci.plugins.workflow:workflow-durable-task-step. A fix is available for org.jenkins-ci.plugins.workflow:workflow-durable-task-step — see the affected versions and patch details below.
Incorrect permission checks in Pipeline: Nodes and Processes plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins.workflow:workflow-durable-task-stepReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
On Jenkins instances with Authorize Project plugin, the authentication associated with a build may lack the Computer/Build permission on some agents. This did not prevent the execution of Pipeline node blocks on those agents due to incorrect permissions checks in Pipeline: Nodes and Processes plugin 2.17 and earlier.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins.workflow:workflow-durable-task-step | all versions | 2.18org.jenkins-ci.plugins.workflow:workflow-durable-task-step:2.18 |
Affected Products
pipeline nodes and processesjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-durable-task-step, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins.workflow:workflow-durable-task-step to 2.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000015 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2018-1000015 in your dependencies?
Find it across Maven, including transitive dependencies.