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.

The remote Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4781-1 advisory.

  - 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. (CVE-2016-10030)

  - 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.
    (CVE-2017-15566)

  - SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmDBD.
    (CVE-2018-7033)

  - 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). (CVE-2018-10995)

  - SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems. (CVE-2019-6438)

  - Slurm 19.05.x before 19.05.7 and 20.02.x before 20.02.3, in the rare case where Message Aggregation is     enabled, allows Authentication Bypass via an Alternate Path or Channel. A race condition allows a user to     launch a process as an arbitrary user. (CVE-2020-12693)

  - Slurm before 19.05.8 and 20.x before 20.02.6 has an RPC Buffer Overflow in the PMIx MPI plugin.
    (CVE-2020-27745)

  - Slurm before 19.05.8 and 20.x before 20.02.6 exposes Sensitive Information to an Unauthorized Actor     because xauth for X11 magic cookies is affected by a race condition in a read operation on the /proc     filesystem. (CVE-2020-27746)

  - SchedMD Slurm before 20.02.7 and 20.03.x through 20.11.x before 20.11.7 allows remote code execution as     SlurmUser because use of a PrologSlurmctld or EpilogSlurmctld script leads to environment mishandling.
    (CVE-2021-31215)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 16.04 ESM host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4781-2 advisory.

  - 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. (CVE-2016-10030)

  - 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). (CVE-2018-10995)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

This update for pdsh, slurm_20_02 fixes the following issues :

Changes in slurm_20_02 :

Add support for openPMIx also for Leap/SLE 15.0/1 (bsc#1173805).

Do not run %check on SLE-12-SP2: Some incompatibility in tcl makes this fail.

Remove unneeded build dependency to postgresql-devel.

Disable build on s390 (requires 64bit).

Bring QA to the package build: add %%check stage.

Remove cruft that isn't needed any longer.

Add 'ghosted' run-file.

Add rpmlint filter to handle issues with library packages for Leap and enterprise upgrade versions.

Updated to 20.02.3 which fixes CVE-2020-12693 (bsc#1172004).

Other changes are :

  - Factor in ntasks-per-core=1 with cons_tres.

  - Fix formatting in error message in cons_tres.

  - Fix calling stat on a NULL variable.

  - Fix minor memory leak when using reservations with     flags=first_cores.

  - Fix gpu bind issue when CPUs=Cores and ThreadsPerCore >     1 on a node.

  - Fix --mem-per-gpu for heterogenous --gres requests.

  - Fix slurmctld load order in load_all_part_state().

  - Fix race condition not finding jobacct gather task     cgroup entry.

  - Suppress error message when selecting nodes on disjoint     topologies.

  - Improve performance of _pack_default_job_details() with     large number of job

  - arguments.

  - Fix archive loading previous to 17.11 jobs per-node     req_mem.

  - Fix regresion validating that --gpus-per-socket requires

    --sockets-per-node

  - for steps. Should only validate allocation requests.

  - error() instead of fatal() when parsing an invalid     hostlist.

  - nss_slurm - fix potential deadlock in slurmstepd on     overloaded systems.

  - cons_tres - fix --gres-flags=enforce-binding and related

    --cpus-per-gres.

  - cons_tres - Allocate lowest numbered cores when     filtering cores with gres.

  - Fix getting system counts for named GRES/TRES.

  - MySQL - Fix for handing typed GRES for association     rollups.

  - Fix step allocations when tasks_per_core > 1.

  - Fix allocating more GRES than requested when asking for     multiple GRES types.

Treat libnss_slurm like any other package: add version string to upgrade package.

Updated to 20.02.1 with following changes'

  - Improve job state reason for jobs hitting     partition_job_depth.

  - Speed up testing of singleton dependencies.

  - Fix negative loop bound in cons_tres.

  - srun - capture the MPI plugin return code from     mpi_hook_client_fini() and use as final return code for     step failure.

  - Fix segfault in cli_filter/lua.

  - Fix --gpu-bind=map_gpu reusability if tasks > elements.

  - Make sure config_flags on a gres are sent to the     slurmctld on node registration.

  - Prolog/Epilog - Fix missing GPU information.

  - Fix segfault when using config parser for expanded     lines.

  - Fix bit overlap test function.

  - Don't accrue time if job begin time is in the future.

  - Remove accrue time when updating a job start/eligible     time to the future.

  - Fix regression in 20.02.0 that broke --depend=expand.

  - Reset begin time on job release if it's not in the     future.

  - Fix for recovering burst buffers when using     high-availability.

  - Fix invalid read due to freeing an incorrectly allocated     env array.

  - Update slurmctld -i message to warn about losing data.

  - Fix scontrol cancel_reboot so it clears the DRAIN flag     and node reason for a pending ASAP reboot.

Changes in pdsh: Bring QA to the package build: add %%check stage

Since the build for the SLE-12 HPC Module got fixed, simplify spec file and remove legacy workarounds.

Remove _multibuild file where not needed.

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for pdsh, slurm_18_08 fixes the following issues :

Slurm was included in the 18.08 release, as 'slurm_18_08' package. The version 18.08.9 contains all recent security fixes, including :

CVE-2019-19728: Fixed a privilege escalation with srun, where --uid might have unintended side effects (bsc#1159692).

CVE-2019-19727: Fixed permissions of slurmdbd.conf (bsc#1155784).

pdsh was updated to: Add support for an alternative SLURM version when building the slurm plugin.

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

With this vulnerability arbitrary files can be overwritten on nodes running jobs provided that the user can run a job that is able to trigger a failure of a Prolog script.

For Debian 7 'Wheezy', these problems have been fixed in version 2.3.4-2+deb7u1.

We recommend that you upgrade your slurm-llnl packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
183132	Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM : Slurm vulnerabilities (USN-4781-1)	Nessus	Ubuntu Local Security Checks	critical
170923	Ubuntu 16.04 ESM : Slurm vulnerabilities (USN-4781-2)	Nessus	Ubuntu Local Security Checks	high
147801	SUSE SLES12 Security Update : slurm_20_11 / pdsh (SUSE-SU-2021:0773-1)	Nessus	SuSE Local Security Checks	critical
143870	SUSE SLES12 Security Update : pdsh, slurm_20_02 (SUSE-SU-2020:2607-1)	Nessus	SuSE Local Security Checks	critical
134036	SUSE SLED15 / SLES15 Security Update : pdsh, slurm_18_08 (SUSE-SU-2020:0443-1)	Nessus	SuSE Local Security Checks	critical
133949	SUSE SLES12 Security Update : pdsh, slurm_18_08 (SUSE-SU-2020:0434-1)	Nessus	SuSE Local Security Checks	critical
99715	Debian DLA-921-1 : slurm-llnl security update	Nessus	Debian Local Security Checks	high

Detections

Analytics

CVE-2016-10030

high

Tenable Plugins

critical

high

critical

critical

critical

critical

high