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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade slurm-llnl | May 1, 2017 | Jan 5, 2017 |
| Suse | — | Upgrade slurm_20_11-configUpgrade pdsh-gendersUpgrade libnss_slurm2_20_02Upgrade slurm_18_08-mungeUpgrade slurm-mungeUpgrade slurm_20_11-docUpgrade slurm_18_08-auth-noneUpgrade slurm_18_08-configUpgrade slurm-slurmdbdUpgrade pdsh-netgroupUpgrade perl-slurmUpgrade slurmUpgrade perl-slurm_20_02Upgrade slurm_20_11-pam_slurmUpgrade slurm_18_08-slurmdbdUpgrade slurm_20_11-develUpgrade slurm_18_08-nodeUpgrade slurm-pluginsUpgrade slurm_20_02-slurmdbdUpgrade slurm_20_11-pluginsUpgrade slurm_20_11-torqueUpgrade slurm_20_02-torqueUpgrade slurm_20_02-configUpgrade slurm_20_11-sviewUpgrade slurm_20_11-sqlUpgrade slurm_20_11-luaUpgrade slurm-docUpgrade slurm_20_11-auth-noneUpgrade perl-slurm_18_08Upgrade slurm-sched-wikiUpgrade libslurm36Upgrade pdsh-slurm_20_11Upgrade slurm_20_02-develUpgrade slurm_20_02-pluginsUpgrade slurm_20_02-config-manUpgrade perl-slurm_20_11Upgrade libpmi0_20_02Upgrade slurm_20_02Upgrade slurm_20_02-docUpgrade libnss_slurm2_20_11Upgrade libpmi0_18_08Upgrade slurm_18_08-develUpgrade slurm_18_08-pam_slurmUpgrade slurm_18_08Upgrade slurm_20_02-luaUpgrade pdsh-slurm_18_08Upgrade pdsh-dshgroupUpgrade slurm_20_02-sviewUpgrade slurm_20_02-sqlUpgrade pdsh-slurm_20_02Upgrade slurm-pam_slurmUpgrade slurm_20_11-config-manUpgrade libslurm29Upgrade slurm-luaUpgrade libpmi0_20_11Upgrade slurm_20_11-slurmdbdUpgrade pdshUpgrade slurm-develUpgrade slurm-auth-noneUpgrade slurm_18_08-docUpgrade slurm_20_02-pam_slurmUpgrade slurm_20_11-webdocUpgrade libslurm35Upgrade slurm_18_08-pluginsUpgrade slurm_20_02-mungeUpgrade slurm_20_02-auth-noneUpgrade pdsh-slurmUpgrade pdsh-machinesUpgrade slurm_20_11Upgrade slurm_18_08-sqlUpgrade slurm_20_11-mungeUpgrade slurm_20_11-nodeUpgrade libslurm33Upgrade slurm_18_08-luaUpgrade slurm_18_08-torqueUpgrade slurm_20_02-node | Jun 9, 2021 | Jan 5, 2017 |
| Ubuntu | — | Upgrade slurm-wlm-emulator (Ubuntu Pro)Upgrade libslurmdb29 (Ubuntu Pro)Upgrade libpam-slurm (Ubuntu Pro)Upgrade slurm-llnl-slurmdbd (Ubuntu Pro)Upgrade slurmdbd (Ubuntu Pro)Upgrade libpmi0 (Ubuntu Pro)Upgrade slurmd (Ubuntu Pro)Upgrade slurmctld (Ubuntu Pro)Upgrade slurm-client (Ubuntu Pro)Upgrade slurm-wlm-torque (Ubuntu Pro)Upgrade sview (Ubuntu Pro)Upgrade libslurm-perl (Ubuntu Pro)Upgrade slurm-wlm (Ubuntu Pro)Upgrade libslurm29 (Ubuntu Pro)Upgrade libslurmdb-perl (Ubuntu Pro)Upgrade slurm-llnl (Ubuntu Pro)Upgrade slurm-client-emulator (Ubuntu Pro)Upgrade slurm-wlm-basic-plugins (Ubuntu Pro) | Mar 22, 2023 | Jan 5, 2017 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub