Debian LinuxOperating system · Debian
CVE-2019-19728
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 · uneditedSchedMD Slurm before 18.08.9 and 19.x before 19.05.5 executes srun --uid with incorrect privileges.
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 confidenceThe vulnerability exists in SchedMD Slurm where the srun command with the --uid flag executes with incorrect privilege handling. This can allow an unprivileged user to potentially execute code with elevated privileges by exploiting the improper uid handling in srun.
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
Debian LinuxOperating system
= 10.0< 18.08.9>= 19.05.0, < 19.05.5= 15.1CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Slurm versionRun 'slurmctld --version' or 'srun --version' to determine the installed version of SchedMD SlurmAffected if The version is less than 18.08.9, OR is 19.05.0 through 19.05.4 (for the 19.x branch)
-
Check srun binary permissionsRun 'ls -la /usr/bin/srun' (or where srun is located) to inspect the permissions on the srun binaryAffected if The srun binary is owned by root and has the setuid bit set, allowing execution with elevated privileges
-
Verify srun access for unprivileged usersRun 'getent group slurm' and check if unprivileged users are members of the slurm group, or test if non-root users can execute srunAffected if Unprivileged users have permission to execute srun and are not restricted by proper access controls
-
Confirm Slurm installation on Debian or OpenSUSEFor Debian: check 'dpkg -l | grep slurm'. For OpenSUSE: check 'rpm -qa | grep slurm'Affected if Running Debian 10.0 or OpenSUSE Leap 15.1 with Slurm installed
You are affected if you are running SchedMD Slurm versions 18.x before 18.08.9, or versions 19.05.0 through 19.05.4, AND unprivileged users have access to the srun command with the --uid flag.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data18.08.919.05.5
Upgrade Slurm to version 18.08.9 or later for the 18.x branch, or version 19.05.5 or later for the 19.x branch. Alternatively, implement proper access controls on srun binary and enforce strict policy until upgrade is feasible.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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