CVE-2023-49937

9.8 CRITICAL

📋 TL;DR

This CVE describes a double-free vulnerability in SchedMD Slurm workload manager that allows attackers to cause denial of service or potentially execute arbitrary code. The vulnerability affects Slurm versions 22.05.x, 23.02.x, and 23.11.x before specific patch releases. Organizations using affected Slurm versions for cluster management are at risk.

💻 Affected Systems

Products:
  • SchedMD Slurm
Versions: 22.05.x before 22.05.11, 23.02.x before 23.02.7, 23.11.x before 23.11.1
Operating Systems: Linux distributions running Slurm
Default Config Vulnerable: ⚠️ Yes
Notes: All configurations running affected Slurm versions are vulnerable regardless of specific settings.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, privilege escalation, and potential lateral movement within the cluster environment.

🟠

Likely Case

Denial of service causing Slurm daemon crashes, disrupting job scheduling and cluster operations until service restart.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls, potentially only affecting availability within isolated segments.

🌐 Internet-Facing: HIGH - Slurm management interfaces exposed to internet could be directly targeted by remote attackers.
🏢 Internal Only: HIGH - Internal attackers or compromised systems could exploit this to disrupt critical cluster operations.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Double-free vulnerabilities typically require specific memory manipulation knowledge but CVSS 9.8 suggests reliable exploitation is feasible.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 22.05.11, 23.02.7, or 23.11.1

Vendor Advisory: https://www.schedmd.com/security-archive.php

Restart Required: Yes

Instructions:

1. Identify current Slurm version using 'slurmd -V' or 'scontrol show config | grep Version'. 2. Download appropriate patched version from SchedMD website. 3. Stop Slurm services. 4. Install updated packages. 5. Restart Slurm services.

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict network access to Slurm daemons to trusted management networks only

iptables -A INPUT -p tcp --dport 6817 -s TRUSTED_NETWORK -j ACCEPT
iptables -A INPUT -p tcp --dport 6817 -j DROP

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Slurm management interfaces from untrusted networks
  • Deploy additional monitoring and alerting for Slurm daemon crashes or abnormal behavior

🔍 How to Verify

Check if Vulnerable:

Run 'slurmd -V' or 'scontrol show config | grep Version' and check if version is in affected range

Check Version:

slurmd -V 2>/dev/null || scontrol show config 2>/dev/null | grep Version

Verify Fix Applied:

Verify version shows 22.05.11, 23.02.7, or 23.11.1 or higher after patching

📡 Detection & Monitoring

Log Indicators:

  • Slurm daemon crashes in syslog
  • Segmentation fault errors in Slurm logs
  • Abnormal memory allocation patterns

Network Indicators:

  • Unexpected connections to Slurm ports (6817-6819)
  • Malformed packets to Slurm services

SIEM Query:

source="slurm.log" AND ("segmentation fault" OR "double free" OR "abort" OR "crash")

🔗 References

📤 Share & Export