Jenkins Build Step Plugin fails to check Item/Build permission

Also known as GHSA-8jx9-7j5m-79x4

Published 9 y ago 2017-10-04 · modified 4 mo ago 2026-06-17 · JSON

CVSS

5.3

v3.0 · NVD

CISA KEV

not known exploited

EPSS

1.0%

percentile 62%

Public exploits

none known

Builds in Jenkins are associated with an authentication that controls the permissions that the build has to interact with other elements in Jenkins. The Pipeline: Build Step Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins.

Exploit prediction (EPSS)

0.96% probability of exploitation in the next 30 days, higher than 62% of all scored CVEs.

CVSS scores

Assigned by	Version	Score	Vector
NVD	3.0	5.3	`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`
NVD	2.0	5.0	`AV:N/AC:L/Au:N/C:N/I:P/A:N`
GitHub	3.0	5.3	`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`

Affected packages

Ecosystem	Package	Affected	Fixed in
maven	`org.jenkins-ci.plugins:pipeline-build-step`	<2.5.1	2.5.1

Classification

Weakness

CWE-276 Incorrect Default Permissions

References

jenkins.io /security/advisory/2017-07-10/ · x_refsource_CONFIRM, x_transferred
nvd.nist.gov /vuln/detail/CVE-2017-1000089 · advisory
jenkins.io /security/advisory/2017-07-10 · web

Sources

CVE List: CVE-2017-1000089
GitHub Advisory: GHSA-8jx9-7j5m-79x4
NVD: CVE-2017-1000089

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.