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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 8.1, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from schedmd organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-01-05T11:59:00.133
2025-04-12T10:46:40.837
Deferred
CVSSv3.0: 8.1 (HIGH)
AV:N/AC:H/Au:N/C:C/I:C/A:C
4.9
10.0
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | schedmd | slurm | ≤ 15.08.12 | Yes |
| Application | schedmd | slurm | 16.05.0 | Yes |
| Application | schedmd | slurm | 16.05.0 | Yes |
| Application | schedmd | slurm | 16.05.0 | Yes |
| Application | schedmd | slurm | 16.05.0 | Yes |
| Application | schedmd | slurm | 16.05.0 | Yes |
| Application | schedmd | slurm | 16.05.1 | Yes |
| Application | schedmd | slurm | 16.05.2 | Yes |
| Application | schedmd | slurm | 16.05.3 | Yes |
| Application | schedmd | slurm | 16.05.4 | Yes |
| Application | schedmd | slurm | 16.05.5 | Yes |
| Application | schedmd | slurm | 16.05.6 | Yes |
| Application | schedmd | slurm | 17.02.0 | Yes |
| Application | schedmd | slurm | 17.02.0 | Yes |
| Application | schedmd | slurm | 17.02.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For schedmd's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.