The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7…
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-284.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
CPE configurations NVD · 15
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:schedmd:slurm:*:*:*:*:*:*:*:* | up to 15.08.12 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.0:*:*:*:*:*:*:* | 16.05.0 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.0:pre1:*:*:*:*:*:* | 16.05.0 pre1 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.0:pre2:*:*:*:*:*:* | 16.05.0 pre2 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.0:rc1:*:*:*:*:*:* | 16.05.0 rc1 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.0:rc2:*:*:*:*:*:* | 16.05.0 rc2 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.1:*:*:*:*:*:*:* | 16.05.1 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.2:*:*:*:*:*:*:* | 16.05.2 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.3:*:*:*:*:*:*:* | 16.05.3 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.4:*:*:*:*:*:*:* | 16.05.4 | Vulnerable | SchedMD |
- cpe:2.3:a:schedmd:slurm:*:*:*:*:*:*:*:* Versions up to 15.08.12 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.0:*:*:*:*:*:*:* Versions 16.05.0 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.0:pre1:*:*:*:*:*:* Versions 16.05.0 pre1 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.0:pre2:*:*:*:*:*:* Versions 16.05.0 pre2 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.0:rc1:*:*:*:*:*:* Versions 16.05.0 rc1 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.0:rc2:*:*:*:*:*:* Versions 16.05.0 rc2 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.1:*:*:*:*:*:*:* Versions 16.05.1 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.2:*:*:*:*:*:*:* Versions 16.05.2 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.3:*:*:*:*:*:*:* Versions 16.05.3 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.4:*:*:*:*:*:*:* Versions 16.05.4 Vulnerable ·SchedMD
Show 5 more CPE
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:schedmd:slurm:16.05.5:*:*:*:*:*:*:* | 16.05.5 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:16.05.6:*:*:*:*:*:*:* | 16.05.6 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:17.02.0:pre1:*:*:*:*:*:* | 17.02.0 pre1 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:17.02.0:pre2:*:*:*:*:*:* | 17.02.0 pre2 | Vulnerable | SchedMD |
| cpe:2.3:a:schedmd:slurm:17.02.0:pre3:*:*:*:*:*:* | 17.02.0 pre3 | Vulnerable | SchedMD |
- cpe:2.3:a:schedmd:slurm:16.05.5:*:*:*:*:*:*:* Versions 16.05.5 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:16.05.6:*:*:*:*:*:*:* Versions 16.05.6 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:17.02.0:pre1:*:*:*:*:*:* Versions 17.02.0 pre1 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:17.02.0:pre2:*:*:*:*:*:* Versions 17.02.0 pre2 Vulnerable ·SchedMD
- cpe:2.3:a:schedmd:slurm:17.02.0:pre3:*:*:*:*:*:* Versions 17.02.0 pre3 Vulnerable ·SchedMD
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2016-10030
- 2026-10-03 Alias added: GHSA-9w2c-9wm9-hvcg
References
More SchedMD Slurm vulnerabilities
- TI-2019-09617 SchedMD Slurm 17.11.x, 18.08.0 through 18.08.7, and 19.05.0 allows SQL Injection. CVSS 3.1CRITICAL 9.8
- TI-2019-04508 SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems. CVSS 3.0CRITICAL 9.8
- TI-2022-11963 SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control that leads to Escalation of Privileges. CVSS 3.1CRITICAL 9.8
- TI-2020-16830 Slurm before 19.05.8 and 20.x before 20.02.6 has an RPC Buffer Overflow in the PMIx MPI plugin. CVSS 3.1CRITICAL 9.8
- TI-2018-05107 SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmDBD. CVSS 3.0CRITICAL 9.8
- TI-2023-27304 An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. CVSS 3.1CRITICAL 9.8
Sources
- CVE-2016-10030 · CVE Program
- CVE-2016-10030 · NVD
- FIRST EPSS
- GHSA-9w2c-9wm9-hvcg · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences