LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10995: SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles user names (aka user_name fields) and g...

SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles user names (aka user_name fields) and group ids (aka gid fields).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This issue affects older SchedMD Slurm cluster scheduler releases that mishandle submitted user names and group IDs. For organizations running Slurm on shared compute clusters, that is concerning because identity and group data are part of job authorization, accounting, and isolation decisions. The public bundle does not provide severity, CVSS, or detailed impact.

Executive priority

Give this medium operational priority if Slurm exists in your environment, especially on shared compute clusters. The available evidence is insufficient to rate urgency higher, but identity-field mishandling in a scheduler warrants timely remediation.

Technical view

CVE-2018-10995 is described as improper handling of Slurm user_name and gid fields in Slurm before 17.02.11 and 17.1x.x before 17.11.7. The bundle does not name a CWE, root cause, exploit primitive, or confirmed security outcome. Debian and SchedMD advisories are listed as remediation references.

Likely exposure

Exposure is most likely in HPC, research, academic, government, or enterprise compute environments running SchedMD Slurm versions older than 17.02.11 or 17.11.7. Internet exposure is not established by the provided sources.

Exploitation context

The source bundle does not state active exploitation, public exploit availability, or inclusion in CISA KEV. Treat exploitation status as unconfirmed. Validation should focus on version inventory and whether Slurm is used in multi-user environments.

Researcher notes

The public bundle is sparse: no CVSS, CWE, exploit description, or detailed impact is provided. Analysis should stay constrained to the stated user_name and gid mishandling and the affected version boundaries. Do not infer privilege escalation or remote exploitability without advisory text supporting it.

Mitigation direction

  • Inventory Slurm versions across controllers, compute nodes, and package repositories.
  • Upgrade Slurm to a non-affected version per SchedMD or distribution guidance.
  • For Debian systems, review DSA-4254 and related LTS advisories.
  • Prioritize shared multi-user clusters where identity handling has higher impact.
  • Check vendor notes before applying backports or regression updates.

Validation and detection

  • Confirm whether any environment runs Slurm before 17.02.11 or 17.11.7.
  • Verify installed packages against Debian or SchedMD advisory versions.
  • Review Slurm controller and node package consistency after updates.
  • Check change records for any Debian LTS regression update follow-up.
  • Document compensating controls if immediate upgrade is not possible.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

cve · low confidence lookup

CVE-2018-10995 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
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
6Source links

CVSS and timeline data

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

Source materials

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.