Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1482094 - (CVE-2017-1000108) CVE-2017-1000108 jenkins-plugin-pipeline-input-step: Input Step Plugin allows users with read access to interact with the step by default
CVE-2017-1000108 jenkins-plugin-pipeline-input-step: Input Step Plugin allows...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170807,reported=2...
: Security
Depends On:
Blocks: 1482096
  Show dependency treegraph
 
Reported: 2017-08-16 08:50 EDT by Adam Mariš
Modified: 2017-09-08 07:46 EDT (History)
7 users (show)

See Also:
Fixed In Version: jenkins-plugin-pipeline-input-step 2.8
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-16 14:27:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-08-16 08:50:16 EDT
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 users are required to have the Item/Build permission by default.

External References:

https://jenkins.io/security/advisory/2017-08-07/
Comment 1 Kurt Seifried 2017-08-16 14:25:49 EDT
Statement:

Deferred (Low security impact)
=======================================
This issue affects the versions of jenkins-plugin-script-security as shipped with Red Hat OpenShift Enterprise. 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.