CVE-2017-1000089: Jenkins Pipeline: Build Step Plugin Authentication Bypass
Summary
CVE-2017-1000089: Jenkins Build Step Plugin fails to check Item/Build permission. Affects org.jenkins-ci.plugins:pipeline-build-step versions < 2.5.1. Fixed in 2.5.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins Pipeline: Build Step Plugin is a Maven-based plugin that allows users to define and execute build steps in Jenkins pipelines. It provides a flexible and powerful way to automate build processes. However, a vulnerability in versions 2.5 and below of the plugin allows unauthorized users to trigger builds in Jenkins, bypassing the authentication and permission checks.
Vulnerability Detail
The vulnerability arises from the plugin's failure to properly check the authentication and permissions of the build. This allows an attacker to trigger any project in Jenkins, potentially leading to unauthorized access, data leakage, or disruption of build processes. The vulnerability has a CVSS score of 5.3, indicating a moderate severity.
How To Fix
Minimum fixed version
2.5.1
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is recommended to upgrade to the latest version of the plugin as soon as possible.
Conclusion
The Jenkins Pipeline: Build Step Plugin is vulnerable to an authentication bypass issue that allows unauthorized triggering of builds. Users should upgrade to version 2.5.1 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:pipeline-build-step →
FAQ
The vulnerability allows unauthorized users to trigger builds in Jenkins, potentially leading to unauthorized access, data leakage, or disruption of build processes.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your pom.xml file and the playground will alert you in real-time if your application is vulnerable.
Yes, upgrading to version 2.5.1 or later of the Pipeline: Build Step Plugin will fix this vulnerability.
There are no known workarounds for this vulnerability. It is recommended to upgrade to the latest version of the plugin.
You can find more information about this vulnerability in the GitHub Security Advisory GHSA-8jx9-7j5m-79x4 (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-8jx9-7j5m-79x4/GHSA-8jx9-7j5m-79x4.json).
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:pipeline-build-step.
