The calculated severity for CVEs has been updated to use CVSS v3 by default. CVEs that do not have a CVSS v3 score will fall back CVSS v2 for calculating severity. Severity display preferences can be toggled in the settings dropdown.
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 user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 ("success") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. If you do not have a Prolog set you are unaffected by this issue.
Base Score: 7.6
Impact Score: 10
Exploitability Score: 4.9
Base Score: 8.1
Impact Score: 5.9
Exploitability Score: 2.2
cpe:2.3:a:schedmd:slurm:*:*:*:*:*:*:*:* versions up to 15.08.12 (inclusive)
|147801||SUSE SLES12 Security Update : slurm_20_11 / pdsh (SUSE-SU-2021:0773-1)||Nessus||SuSE Local Security Checks|
|143870||SUSE SLES12 Security Update : pdsh, slurm_20_02 (SUSE-SU-2020:2607-1)||Nessus||SuSE Local Security Checks|
|134036||SUSE SLED15 / SLES15 Security Update : pdsh, slurm_18_08 (SUSE-SU-2020:0443-1)||Nessus||SuSE Local Security Checks|
|133949||SUSE SLES12 Security Update : pdsh, slurm_18_08 (SUSE-SU-2020:0434-1)||Nessus||SuSE Local Security Checks|
|99715||Debian DLA-921-1 : slurm-llnl security update||Nessus||Debian Local Security Checks|