Bug 1728859

Summary: CVE-2019-12838 Security 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: 30CC: mrehak, pkdevel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 18.08.8 slurm-18.08.8-1.fc30 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-24 00:58:28 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:
Bug Depends On:    
Bug Blocks: 1735929    

Description Philip Kovacs 2019-07-10 19:38:44 UTC 
Description of problem:

CVE-2019-12838 Security vulnerability 

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

19.05.0


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Fixed in 19.05.1
Comment 1 Fedora Update System 2019-07-15 22:15:05 UTC 
FEDORA-2019-5d0d2619df has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5d0d2619df
Comment 2 Fedora Update System 2019-07-16 00:54:34 UTC 
slurm-18.08.8-1.fc30 has been pushed to the Fedora 30 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-2019-5d0d2619df
Comment 3 Fedora Update System 2019-07-24 00:58:28 UTC 
slurm-18.08.8-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Comment 4 Philip Kovacs 2019-08-01 19:31:29 UTC 
*** Bug 1735941 has been marked as a duplicate of this bug. ***