Schedmd Slurm vulnerabilities
25 known vulnerabilities affecting schedmd/slurm.
Total CVEs
25
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL7HIGH12MEDIUM5LOW1
Vulnerabilities
Page 2 of 2
CVE-2019-6438CRITICALCVSS 9.8fixed in 17.11.13≥ 18.08.0, < 18.08.52019-01-31
CVE-2019-6438 [CRITICAL] CVE-2019-6438: SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.
SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.
nvd
CVE-2018-10995MEDIUMCVSS 5.3≤ 17.02.10.1v17.11.0.0+9 more2018-05-30
CVE-2018-10995 [MEDIUM] CWE-20 CVE-2018-10995: SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles user names (aka user_name fields
SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles user names (aka user_name fields) and group ids (aka gid fields).
nvd
CVE-2018-7033CRITICALCVSS 9.8fixed in 17.02.10.0≥ 17.11.0.0, < 17.11.5.0+1 more2018-03-15
CVE-2018-7033 [CRITICAL] CWE-89 CVE-2018-7033: SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmD
SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmDBD.
nvd
CVE-2017-15566HIGHCVSS 7.8fixed in 16.05.11≥ 17.02.0, < 17.2.09+1 more2017-11-01
CVE-2017-15566 [HIGH] CWE-426 CVE-2017-15566: Insecure SPANK environment variable handling exists in SchedMD Slurm before 16.05.11, 17.x before 17
Insecure SPANK environment variable handling exists in SchedMD Slurm before 16.05.11, 17.x before 17.02.9, and 17.11.x before 17.11.0rc2, allowing privilege escalation to root during Prolog or Epilog execution.
nvd
CVE-2016-10030HIGHCVSS 8.1≤ 15.08.12v16.05.0+7 more2017-01-05
CVE-2016-10030 [HIGH] CWE-284 CVE-2016-10030: The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x b
The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the
nvd
← Previous2 / 2