Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1524945 - (CVE-2017-1000505) CVE-2017-1000505 jenkins-plugin-script-security: Arbitrary file read vulnerability in Script Security Plugin (SECURITY-663)
CVE-2017-1000505 jenkins-plugin-script-security: Arbitrary file read vulnerab...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20171211,repor...
: Security
Depends On: 1524946 1565185
Blocks: 1524947
  Show dependency treegraph
 
Reported: 2017-12-12 05:39 EST by Adam Mariš
Modified: 2018-06-29 18:30 EDT (History)
12 users (show)

See Also:
Fixed In Version: jenkins-plugin-script-security 1.37
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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-12-12 05:39:12 EST
Users with the ability to configure sandboxed Groovy and Pipeline scripts, including those from SCM, are able to use a type coercion feature in Groovy to create new File objects from strings. This allowed reading arbitrary files on the Jenkins master file system.

Affected versions: Script Security Plugin up to and including 1.36

External References:

https://jenkins.io/security/advisory/2017-12-11/
Comment 1 Adam Mariš 2017-12-12 05:39:40 EST
Created jenkins-script-security-plugin tracking bugs for this issue:

Affects: fedora-all [bug 1524946]
Comment 4 Andrej Nemec 2018-05-14 08:17:00 EDT
Statement:

This issue affects the versions of jenkins-plugin-script-security as shipped with Red Hat Enterprise OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having security impact of Moderate. 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.