Slurm up to 15.08.12/16.05.6/17.02.0-pre3 Prolog Script Failure slurmd/req.c _prolog_error access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Slurm up to 15.08.12/16.05.6/17.02.0-pre3. This vulnerability affects the function _prolog_error of the file slurmd/req.c of the component Prolog Script Failure Handler. Performing a manipulation results in access control.
This vulnerability was named CVE-2016-10030. The attack may be initiated remotely. There is no available exploit.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Slurm up to 15.08.12/16.05.6/17.02.0-pre3. This affects the function _prolog_error of the file slurmd/req.c of the component Prolog Script Failure Handler. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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 bug was discovered 12/22/2016. The weakness was presented 01/05/2017 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2016-10030 since 12/22/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 99715 (Debian DLA-921-1 : slurm-llnl security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l.
Upgrading to version 15.08.13, 16.05.7 or 17.02.0-pre4 eliminates this vulnerability. A possible mitigation has been published 4 months after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (99715) and SecurityFocus (BID 95299†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Not Affected
- Slurm up to 0.5.x
Product
Name
Version
- 15.08.0
- 15.08.1
- 15.08.2
- 15.08.3
- 15.08.4
- 15.08.5
- 15.08.6
- 15.08.7
- 15.08.8
- 15.08.9
- 15.08.10
- 15.08.11
- 15.08.12
- 16.05.0
- 16.05.1
- 16.05.2
- 16.05.3
- 16.05.4
- 16.05.5
- 16.05.6
- 17.02.0-pre3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 99715
Nessus Name: Debian DLA-921-1 : slurm-llnl security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 803020
OpenVAS Name: Debian LTS Advisory ([SECURITY] [DLA 921-1] slurm-llnl security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Slurm 15.08.13/16.05.7/17.02.0-pre4
Patch: github.com
Timeline
12/22/2016 🔍12/22/2016 🔍
01/05/2017 🔍
01/05/2017 🔍
01/05/2017 🔍
01/05/2017 🔍
04/27/2017 🔍
04/28/2017 🔍
10/27/2022 🔍
Sources
Advisory: 92362a92fffe60187df61f99ab11c249d44120ee⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-10030 (🔍)
GCVE (CVE): GCVE-0-2016-10030
GCVE (VulDB): GCVE-100-95043
SecurityFocus: 95299 - Slurm CVE-2016-10030 Security Bypass Vulnerability
OSVDB: - CVE-2016-10030 - Slurm - Privilege Escalation Issue
Entry
Created: 01/05/2017 15:44Updated: 10/27/2022 16:22
Changes: 01/05/2017 15:44 (81), 10/27/2022 16:22 (4)
Complete: 🔍
Cache ID: 216:846:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.