Bug 1508645

Summary: CVE-2017-15566 slurm: privilege escalation vulnerability
Product: [Fedora] Fedora Reporter: Philip Kovacs <pkdevel>
Component: slurmAssignee: Philip Kovacs <pkdevel>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: pkdevel
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://nvd.nist.gov/vuln/detail/CVE-2017-15566
Whiteboard:
Fixed In Version: slurm-17.02.9-1 slurm-17.02.9-2.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-10 00:46:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Philip Kovacs 2017-11-01 20:41:41 UTC
Description of problem:

https://nvd.nist.gov/vuln/detail/CVE-2017-15566

Version-Release number of selected component (if applicable):

slurm version 17.02.8 and earlier

How reproducible:

Not disclosed.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Upstream version 17.02.9 closes the issue.

Comment 1 Fedora Update System 2017-11-01 23:06:38 UTC
slurm-17.02.9-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4dad5165dc

Comment 2 Fedora Update System 2017-11-04 18:02:19 UTC
slurm-17.02.9-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4dad5165dc

Comment 3 Fedora Update System 2017-11-11 03:11:35 UTC
slurm-17.02.9-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.