Bug 1471050 (CVE-2017-1000089) - CVE-2017-1000089 jenkins-plugin-pipeline-build-step: Missing check of Item/Build permission (SECURITY-433)
Summary: CVE-2017-1000089 jenkins-plugin-pipeline-build-step: Missing check of Item/Bu...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-1000089
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1472030
Blocks: 1471067
TreeView+ depends on / blocked
 
Reported: 2017-07-14 10:12 UTC by Adam Mariš
Modified: 2021-02-17 01:56 UTC (History)
13 users (show)

Fixed In Version: jenkins-plugin-pipeline-build-step 2.5.1
Doc Type: If docs needed, set a value
Doc Text:
The jenkins-plugin-pipeline-build-step fails to check permissions correctly allowing attackers with access to it to specify the triggering of any other project in Jenkins. This potentially gives an attacker access to projects they should not have access to.
Clone Of:
Environment:
Last Closed: 2017-08-14 16:43:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Mariš 2017-07-14 10:12:03 UTC
Builds in Jenkins are associated with an authentication that controls the permissions that the build has to interact with other elements in Jenkins. By default, builds run as SYSTEM and are unconstrained unless plugins implement specific additional permission checks.

Plugins like Authorize Project Plugin allow changing the authentication associated with a build.

The Pipeline: Build Step Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins.

External References:

https://jenkins.io/security/advisory/2017-07-10/

Comment 1 Adam Mariš 2017-07-14 10:12:20 UTC
Acknowledgments:

Name: the Jenkins project

Comment 3 Trevor Jay 2017-08-14 16:43:12 UTC
Statement:

This issue affects the versions of jenkins-plugin-pipeline-build-step as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.


Note You need to log in before you can comment on or make changes to this bug.