LiveActive security incident?Get immediate response
CVE Record

CVE-2020-27745: Slurm before 19.05.8 and 20.x before 20.02.6 has an RPC Buffer Overflow in the PMIx MPI plugin.

Slurm before 19.05.8 and 20.x before 20.02.6 has an RPC Buffer Overflow in the PMIx MPI plugin.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This issue affects Slurm, a workload scheduler commonly used in HPC environments. The flaw is a buffer overflow in the PMIx MPI plugin’s RPC handling. The sources name fixed Slurm version lines but do not provide CVSS, impact details, or confirmed exploitation evidence.

Executive priority

Treat this as a targeted infrastructure maintenance priority for Slurm/HPC environments. There is no sourced active exploitation signal, but affected scheduler infrastructure can be business-critical and fixed version thresholds are available.

Technical view

CVE-2020-27745 is described as an RPC buffer overflow in Slurm’s PMIx MPI plugin. Affected versions are Slurm before 19.05.8 and Slurm 20.x before 20.02.6. The bundle does not identify specific attack prerequisites, affected configurations, CWE, or exploitability details.

Likely exposure

Exposure is most likely in environments running Slurm with the PMIx MPI plugin, especially HPC clusters. Confirm installed Slurm versions and whether PMIx integration is enabled. The source bundle does not identify affected operating systems beyond Debian advisories referencing Slurm security updates.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. Because the issue is in RPC handling, network reachability and Slurm trust boundaries matter, but the sources do not define a concrete attacker model.

Researcher notes

Evidence is sparse: no CVSS, CWE, PoC status, or detailed impact is included. Analysis should stay anchored to the named buffer overflow, affected version ranges, PMIx plugin context, and Debian/SchedMD advisory references.

Mitigation direction

  • Upgrade Slurm to 19.05.8, 20.02.6, or a later fixed release.
  • Apply Debian security updates if using Debian-packaged Slurm.
  • Review SchedMD and distribution advisories for environment-specific guidance.
  • Restrict Slurm control and compute-node RPC exposure to trusted networks.
  • Disable unused PMIx integration if vendor guidance supports doing so.

Validation and detection

  • Inventory Slurm versions across controller, database, login, and compute nodes.
  • Confirm whether the PMIx MPI plugin is installed or enabled.
  • Check Debian advisory coverage for installed package versions.
  • Review Slurm network exposure and access controls around RPC services.
  • Document any clusters still below the fixed version thresholds.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-27745 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.