Safeguard
Vulnerability Analysis•

CVE-2020-36770: Critical Ownership Flaw in the Gentoo Slurm Ebuild

CVE-2020-36770 is a critical ownership flaw in the Gentoo Slurm ebuild through 22.05.3. Check Gentoo bug 631552 and move to a current Slurm package.

Safeguard Security Team
3 min read

CVE-2020-36770 is a critical (CVSS 9.8) flaw in the pkg_postinst step of the Gentoo ebuild for Slurm through 22.05.3. It calls chown on files in the live root filesystem, so the slurm user could become owner of root owned files. Check Gentoo's bug 631552 and GLSA 202409-16.

What's affected

  • The Gentoo ebuild for Slurm through 22.05.3, per the record.
  • The Gentoo bug says the 22.05.3 ebuild reduced a recursive chown to plain chown but a reviewer said it was incomplete. The ebuilds were later removed, a GLSA followed, and Slurm was reintroduced in October 2024.
  • The bug page does not confirm that the later ebuild is fully free of the issue, so read it before relying on it.

The record scores it 9.8 (Critical) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

On Gentoo use the package tools such as qlist or eix to see the installed slurm version, and check for the GLSA with glsa-check. Then review ownership of files under the Slurm paths.

What to do now

  1. Check the installed Slurm ebuild version.
  2. Read Gentoo bug 631552 and the GLSA.
  3. Move to a current, supported Slurm package.
  4. Audit ownership of root files that the slurm user could have touched.
  5. Restrict who can run as the slurm user.

After you patch, record the new version for Gentoo Slurm ebuild in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps this to CWE-732, incorrect permission assignment. Package install scripts run as root. If one hands ownership of files in live system paths to a service account, that account can end up controlling files it should never own.

The score of 9.8 reflects the potential result: a service user taking root owned files. The bug thread, though, describes this as a packaging problem on one distribution, not a flaw in Slurm itself.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Quick check

Is Slurm itself vulnerable?

The record describes the Gentoo ebuild's post install step, not the upstream Slurm scheduler. Other distributions use different packaging.

How do I find every place Gentoo Slurm ebuild is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.