dbcve.org
SlurmApplication · Schedmd

CVE-2023-49934

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 23.11.x. There is SQL Injection against the SlurmDBD database. The fixed version is 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 · moderate confidence

SQL injection vulnerability in SchedMD Slurm 23.11.x allows remote attackers to inject malicious SQL queries through the SlurmDBD (Slurm Database Daemon) component, potentially enabling unauthorized database access, data exfiltration, or data manipulation.

MitigationUpgrade to Slurm version 23.11.1 or later. If immediate patching is not possible, implement network segmentation and restrict access to the SlurmDBD port.

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.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Slurm version
    Run 'scontrol --version' or 'slurmctld --version' to determine the exact version of Slurm software installed in the environment
    Affected if The version is 23.11.x (any minor release of 23.11)
  2. Confirm SlurmDBD component is in use
    Check if the SlurmDBD (slurmdbd) service is installed and running, typically via 'systemctl status slurmdbd' or by reviewing process listings for the slurmdbd daemon
    Affected if SlurmDBD is installed and running as part of the Slurm deployment
  3. Verify SlurmDBD network exposure
    Inspect network listening ports on the system running SlurmDBD (using 'netstat -tlnp' or 'ss -tlnp') to determine if port 6819 (default SlurmDBD port) or a configured custom port is bound to a non-localhost address
    Affected if SlurmDBD is listening on a network-accessible IP address rather than only localhost/127.0.0.1
  4. Review SlurmDBD configuration for authentication
    Examine the SlurmDBD configuration file (typically slurmdbd.conf) to check the AuthInfo, AuthType, or authentication parameters defining how clients authenticate to the database daemon
    Affected if Authentication is configured but uses weak or misconfigured settings that permit unauthenticated or insufficiently validated connections

The environment is affected if Slurm version 23.11.x is installed AND SlurmDBD is network-accessible, enabling external attackers to send malicious SQL queries to the database daemon.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Slurm version 23.11.1 or later. If immediate patching is not possible, implement network segmentation and restrict access to the SlurmDBD port.

Recommended fix High confidence

23.11.1

  1. Download Slurm version 23.11.1 from the official SchedMD website (www.schedmd.com) or repository
  2. Backup the SlurmDB database before proceeding with the upgrade
  3. Stop the slurmdbd service
  4. Upgrade the Slurm packages to version 23.11.1 using your package manager or from source
  5. Review and apply any new configuration changes required by version 23.11.1 as documented in the release notes
  6. Start the slurmdbd service
  7. Verify the upgrade was successful and the service is running properly
Caveat Standard minor version upgrade; review release notes for any database schema changes or configuration adjustments

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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