Incorrect permission checks in Pipeline: Nodes and Processes plugin

MEDIUM 4.8CVE-2018-1000015 · GHSA-9r7f-rqhw-j8h8 · Published 23/01/2018 · updated 17/06/2026

In short

CVE-2018-1000015 is a MEDIUM (CVSS 4.8) vulnerability affecting org.jenkins-ci.plugins.workflow:workflow-durable-task-step, pipeline nodes and processes (jenkins).
Chance of exploitation in the next 30 days (EPSS): 1.0%, higher than 63.9% of all vulnerabilities.
Fix: update to 2.18 or later.

Package	Affected versions	Patched versions
org.jenkins-ci.plugins.workflow:workflow-durable-task-step Maven	`< 2.18`	`2.18`
pipeline nodes and processes jenkins	`≤ 2.17`	No fix yet

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.

NVD 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.

References

nvd.nist.gov/vuln/detail/CVE-2018-1000015 · ADVISORY
jenkins.io/security/advisory/2018-01-22 · WEB
jenkins.io/security/advisory/2018-01-22 · Vendor Advisory

Running one of these products? Scan your site to see whether it exposes a vulnerable version.

Scan my site free

Package

Affected versions

Patched versions

org.jenkins-ci.plugins.workflow:workflow-durable-task-step

Maven

< 2.18

2.18

pipeline nodes and processes

jenkins

≤ 2.17

No fix yet

Description

NVD 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.