dbcve.org
SlurmApplication · Schedmd

CVE-2023-49933

HIGH · 7.5 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 22.05.12 / 23.02.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 22.05.x, 23.02.x, and 23.11.x. There is Improper Enforcement of Message Integrity During Transmission in a Communication Channel. This allows attackers to modify RPC traffic in a way that bypasses message hash checks. The fixed versions are 22.05.11, 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

Slurm's RPC communication channel has improper message integrity enforcement, allowing attackers to modify RPC traffic in transit while bypassing the built-in hash verification checks. This is a man-in-the-middle vulnerability in the message transmission layer.

MitigationUpgrade Slurm to version 22.05.11, 23.02.7, or 23.11.1 to patch the message integrity bypass vulnerability. Verify RPC communications are using authenticated/encrypted channels where possible.

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:>= 22.05, < 22.05.12>= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Determine installed Slurm version
    Run 'slurmctld -V' on the controller node and 'slurmd -V' on compute nodes to get the version numbers.
    Affected if The version falls within >= 22.05 but < 22.05.12, OR >= 23.02 but < 23.02.7, OR equals 23.11.
  2. Verify MUNGE authentication is configured
    Check if the MUNGE socket exists at /var/run/munge/munge.socket.2 and examine the slurm.conf for 'MungeDefault' parameter. Run 'munge -n | unmunge' to test if munge authentication works between nodes.
    Affected if MUNGE is not running or not properly configured, leaving RPC communications unauthenticated.
  3. Inspect Slurm RPC encryption settings
    Examine slurm.conf for 'EncryptionType' setting. Check if 'PrologSlurmctld' or 'EpilogSlurmctld' scripts disable or override authentication. Look for any configuration that disables integrity checking.
    Affected if EncryptionType is not set to 'crypto/task' or similar, or if integrity verification is explicitly disabled in the configuration.
  4. Check network accessibility between Slurm components
    Verify that slurmctld and slurmd communicate over the network accessible to potential attackers (not isolated). Review firewall rules and network segmentation for the Slurm control plane ports (typically 6817/6818).
    Affected if Slurm control communications traverse untrusted network segments where MITM attacks are possible.

The environment is affected if the installed Slurm version is one of the vulnerable releases listed AND RPC communications lack proper authentication/encryption configuration.

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 22.05.12 / 23.02.7 or later
Fixed in 22.05.1223.02.7
Interim mitigation

Upgrade Slurm to version 22.05.11, 23.02.7, or 23.11.1 to patch the message integrity bypass vulnerability. Verify RPC communications are using authenticated/encrypted channels where possible.

Recommended fix High confidence

Upgrade to Slurm 22.05.12, 23.02.7, or 23.11.1 depending on your current branch

  1. 1. Back up the current Slurm configuration files (slurm.conf, cgroup.conf, etc.) and database if using SlurmDBD
  2. 2. Review the release notes for the target version (22.05.12, 23.02.7, or 23.11.1) for any configuration or migration notes
  3. 3. Stop all Slurm services (slurmctld, slurmd, slurmdbd if applicable) on all nodes in the cluster
  4. 4. Upgrade the Slurm packages on all nodes using the distribution's package manager (e.g., yum update slurm or apt install slurm=version)
  5. 5. Ensure the upgraded Slurm binaries match across all nodes in the cluster
  6. 6. Verify the configuration files are intact and compatible with the new version
  7. 7. Start the slurmctld service on the controller node first
  8. 8. Start slurmd services on compute nodes
Caveat Minor version upgrades within the same release series typically have no breaking changes, but review release notes for any configuration or feature changes

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

Fix this in Slurm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49933 — 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-49933 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