dbcve.org
FedoraOperating system · Fedoraproject

CVE-2021-43337

MEDIUM · 6.5 CVSS v3.1 Published 2021-11-17
Fix available
A fix is available. Upgrade to 21.08.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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
SchedMD Slurm 21.08.* before 21.08.4 has Incorrect Access Control. On sites using the new AccountingStoreFlags=job_script and/or job_env options, the access control rules in SlurmDBD may permit users to request job scripts and environment files to which they should not have access.

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

A detailed technical summary for this CVE is being prepared.

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
Affected:= 34= 35
SlurmApplication
Affected:>= 21.08.0, < 21.08.4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 21.08.4 or later
Fixed in 21.08.4
Vendor patch www.schedmd.com →
Recommended fix High confidence

Slurm 21.08.4

  1. 1. Backup your current Slurm configuration files (/etc/slurm/slurm.conf, /etc/slurm/slurmdbd.conf, and any job script templates)
  2. 2. Check your current Slurm version: slurmctld --version
  3. 3. Stop the Slurm services in order: systemctl stop slurmdbd, systemctl stop slurmctld, systemctl stop slurmd
  4. 4. Upgrade Slurm packages to version 21.08.4 or later using your package manager (e.g., dnf update slurm slurm-client slurm-slurmctld slurm-slurmdbd)
  5. 5. Verify the new version is installed: rpm -qa | grep slurm
  6. 6. Start the Slurm services in order: systemctl start slurmd, systemctl start slurmctld, systemctl start slurmdbd
  7. 7. Verify the services are running: systemctl status slurmdbd slurmctld slurmd
  8. 8. Test that the access control issue is resolved by attempting to access job scripts/env files that should be restricted
Caveat Review the release notes at https://www.schedmd.com/news.php?id=256 for any configuration or behavior changes between your current version and 21.08.4

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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