Approved changes feed: RSS · Atom

cpe:2.3:a:schedmd:slurm:16.05.0:rc2:*:*:*:*:*:*

part: a version: 16.05.0 update: rc2

VendorSchedmd (24dc9c51-fc49-5464-9596-f99e842bb20c)
ProductSlurm (48a291ec-5a2b-5faa-8dc9-7a8215c3f5cd)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/schedmd/slurm purl2cpe 2026-06-01 10:14:38.132399
pkg:github/uwb-linux/slurm purl2cpe 2026-06-01 10:14:38.132401
pkg:rpm/fedora/slurm purl2cpe 2026-06-01 10:14:38.132402
pkg:rpm/opensuse/slurm purl2cpe 2026-06-01 10:14:38.132403
pkg:sourceforge/slurm purl2cpe 2026-06-01 10:14:38.132405

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2016-10030 vulnerable 2026-06-08 05:07:17.050871 Details available
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.
Published: 2017-01-05T11:00:00.000Z
Updated: 2024-08-06T03:07:31.955Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.