dbcve.org
SlurmApplication · Schedmd

CVE-2023-49935

HIGH · 8.8 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 23.02.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in SchedMD Slurm 23.02.x and 23.11.x. There is Incorrect Access Control because of a slurmd Message Integrity Bypass. An attacker can reuse root-level authentication tokens during interaction with the slurmd process. This bypasses the RPC message hashes that protect against undesired MUNGE credential reuse. The fixed versions are 23.02.7 and 23.11.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability in SchedMD Slurm's slurmd daemon allows attackers to bypass message integrity controls by reusing root-level authentication tokens. The flaw circumvents RPC message hashes that normally protect against unauthorized MUNGE credential reuse, enabling improper access to the Slurm workload management system.

MitigationUpgrade Slurm to version 23.02.7 or 23.11.1 to patch the message integrity bypass. Given the high CVSS score and root-level token reuse capability, prioritize this upgrade on all affected slurmd nodes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SlurmApplication
Affected:>= 23.02, < 23.02.7= 23.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Slurm is installed
    Run `which slurmd` or check for Slurm packages using your system's package manager (e.g., `rpm -qa | grep slurm` or `dpkg -l | grep slurm`)
    Affected if Slurm is not installed on the system
  2. Determine installed Slurm version
    Run `slurmd --version` or query the package version (e.g., `rpm -q slurm` or `dpkg -s slurm`)
    Affected if The version falls within >= 23.02 but < 23.02.7, or equals exactly 23.11
  3. Confirm slurmd daemon is running
    Run `systemctl status slurmd` or `ps aux | grep slurmd` to check if the slurmd daemon process is active
    Affected if slurmd is actively running on the node
  4. Verify MUNGE authentication is in use
    Check for the presence of the MUNGE socket at /var/run/munge/munge.socket.2 or run `munge -n` to test MUNGE functionality
    Affected if MUNGE authentication is configured and in use (the vulnerability exploits MUNGE credential reuse protection)

You are affected if Slurm slurmd is running and the installed version is 23.02 through 23.02.6 inclusive, or exactly version 23.11, with MUNGE authentication enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.02.7 or later
Fixed in 23.02.7
Interim mitigation

Upgrade Slurm to version 23.02.7 or 23.11.1 to patch the message integrity bypass. Given the high CVSS score and root-level token reuse capability, prioritize this upgrade on all affected slurmd nodes.

Recommended fix High confidence

Upgrade to Slurm 23.02.7 (for 23.02.x versions) or Slurm 23.11.1 (for 23.11 version)

  1. 1. Identify current Slurm version using 'slurmctld --version' or 'scontrol version'
  2. 2. For systems running Slurm >= 23.02 and < 23.02.7: Plan upgrade to version 23.02.7
  3. 3. For systems running Slurm 23.11: Plan upgrade to version 23.11.1
  4. 4. Backup all Slurm configuration files (slurm.conf, cgroup.conf, etc.) and state data
  5. 5. Backup Munge key (/etc/munge/munge.key) if used for authentication
  6. 6. Stop all Slurm services (slurmctld, slurmd) on all nodes
  7. 7. Upgrade Slurm packages using system package manager (e.g., 'dnf update' or 'yum update' for Fedora/RHEL, or appropriate method for your distribution)
  8. 8. Verify new version is installed: 'slurmctld --version'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Slurm Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49935 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49935 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data