FedoraOperating system · Fedoraproject
CVE-2020-12693
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 · uneditedSlurm 19.05.x before 19.05.7 and 20.02.x before 20.02.3, in the rare case where Message Aggregation is enabled, allows Authentication Bypass via an Alternate Path or Channel. A race condition allows a user to launch a process as an arbitrary user.
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 confidenceSlurm workload manager versions 19.05.x before 19.05.7 and 20.02.x before 20.02.3 contains an authentication bypass vulnerability in the Message Aggregation feature. A race condition allows an authenticated user to launch a process as an arbitrary user on the system, effectively escalating privileges by impersonating other users through timing manipulation.
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
FedoraOperating system
= 31= 32
Debian LinuxOperating system
= 9.0= 10.0>= 19.05.0, < 19.05.7>= 20.02.0, < 20.02.3= 15.1= 15.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Slurm versionRun `scontrol version` or `slurmctld --version` to obtain the installed version numberAffected if Version is 19.05.0 through 19.05.6, or 20.02.0 through 20.02.2 (falls within >=19.05.0,<19.05.7 or >=20.02.0,<20.02.3)
-
Verify Message Aggregation is enabledExamine the Slurm configuration file (typically /etc/slurm/slurm.conf) for the MessageAggregation parameter, or run `scontrol show config | grep -i message`Affected if MessageAggregation is set to a value other than 0 or is absent (defaults to enabled in vulnerable versions)
-
Confirm slurmctld daemon is runningRun `systemctl status slurmctld` or check for the slurmctld process with `ps aux | grep slurmctld`Affected if The slurmctld daemon is active, as the vulnerability exists in the server component
You are affected if your Slurm version is 19.05.0-19.05.6 or 20.02.0-20.02.2 AND Message Aggregation is enabled (default).
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 data19.05.720.02.3
Upgrade Slurm to version 19.05.7 or 20.02.3 or later. If immediate upgrading is not feasible, consider disabling Message Aggregation as a temporary workaround, though this may impact performance.
Fix this in Fedora
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12693 — 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-2020-12693 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