CVE-2016-10030: n/a vulnerability

CVE-2016-10030: The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 1...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 03:07 UTC (UTC+00:00)

Security readout for executives and security teams

This Slurm issue matters for HPC clusters that run Prolog scripts before jobs. If a Prolog script fails, an authenticated job user may be able to take control of an arbitrary system file. Sites without a configured Prolog script are described as unaffected. Exposure is likely limited to Slurm compute nodes where Prolog is configured, users can submit jobs, and the Prolog script can fail. Multi-user academic, research, and shared compute clusters should prioritize review. Clusters without Prolog configured are described as unaffected. Prioritize shared Slurm environments with untrusted or semi-trusted users and Prolog enabled. This is not broadly internet-exposed based on the provided evidence, but arbitrary file control on compute nodes can create serious operational and integrity risk in multi-tenant clusters. Mitigation focus: Upgrade Slurm to a fixed or currently supported vendor release.; Confirm fixes cover 15.08.13, 16.05.7, or 17.02.0-pre4 thresholds.; If unable to upgrade, disable Prolog scripts where operationally feasible..

Prepared: Jun 13, 2026, 12:51 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2016-10030 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jan 5, 2017, 11:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120eeCVE reference · x_refsource_CONFIRM
https://www.schedmd.com/news.php?id=178CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.