First published: Wed Oct 04 2017(Updated: )
The Pipeline: Input Step Plugin by default allowed users with Item/Read access to a pipeline to interact with the step to provide input. This has been changed, and now requires users to have the Item/Build permission instead.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Pipeline-input-step | =2.0 | |
Jenkins Pipeline-input-step | =2.1 | |
Jenkins Pipeline-input-step | =2.2 | |
Jenkins Pipeline-input-step | =2.3 | |
Jenkins Pipeline-input-step | =2.4 | |
Jenkins Pipeline-input-step | =2.5 | |
Jenkins Pipeline-input-step | =2.6 | |
Jenkins Pipeline-input-step | =2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000108 has been classified as a medium severity vulnerability.
To fix CVE-2017-1000108, ensure that users have Item/Build permissions rather than just Item/Read access.
CVE-2017-1000108 affects versions 2.0 to 2.7 of the Jenkins Pipeline Input Step plugin.
CVE-2017-1000108 changed the permissions required for users to provide input during a pipeline run.
Users of the Jenkins Pipeline Input Step plugin who have only Item/Read permissions are impacted by CVE-2017-1000108.