CVE-2016-10030: High severity slurm workload manager vulnerability

Published Jan 5, 2017
·
Updated

The prologerror 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.

Affected Software

15 affected components
SchedMD Slurm<=15.08.12
SchedMD Slurm=16.05.0
SchedMD Slurm=16.05.0-pre1
SchedMD Slurm=16.05.0-pre2
SchedMD Slurm=16.05.0-rc1
SchedMD Slurm=16.05.0-rc2
SchedMD Slurm=16.05.1
SchedMD Slurm=16.05.2
SchedMD Slurm=16.05.3
SchedMD Slurm=16.05.4
SchedMD Slurm=16.05.5
SchedMD Slurm=16.05.6
SchedMD Slurm=17.02.0-pre1
SchedMD Slurm=17.02.0-pre2
SchedMD Slurm=17.02.0-pre3

Event History

Jan 5, 2017
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-10030?

CVE-2016-10030 is considered a high severity vulnerability due to its potential to allow unauthorized file access.

2

How do I fix CVE-2016-10030?

To fix CVE-2016-10030, upgrade Slurm to version 15.08.13 or later, 16.05.7 or later, or 17.02.0-pre4 or later.

3

What software is affected by CVE-2016-10030?

CVE-2016-10030 affects Slurm versions prior to 15.08.13, 16.x versions prior to 16.05.7, and 17.x versions prior to 17.02.0-pre4.

4

Can CVE-2016-10030 lead to privilege escalation?

Yes, CVE-2016-10030 can potentially lead to privilege escalation by allowing a user to control arbitrary files.

5

What component of Slurm is affected by CVE-2016-10030?

The vulnerability specifically affects the _prolog_error function in the slurmd daemon.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203