# CVE-2020-12693: Race condition in n/a

> A race condition in Slurm allows arbitrary user process launch when Message Aggregation is enabled, leading to privilege escalation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9rpg-w3f6-9mpm, SUSE-SU-2020:1554-1, SUSE-SU-2020:2598-1, SUSE-SU-2020:2599-1, SUSE-SU-2020:2600-1, UBUNTU-CVE-2020-12693, openSUSE-SU-2020:1421-1, openSUSE-SU-2020:1468-1, openSUSE-SU-2020:1969-1

## What is CVE-2020-12693?

CVE-2020-12693 is a high-severity vulnerability in Debian Debian Linux, published on 21 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Slurm 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.

## Which versions are affected by CVE-2020-12693?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `slurm_18_08` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 18.08.9-1.8.2 |
| `slurm_18_08` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 18.08.9-1.8.2 |
| `slurm_18_08` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 18.08.9-3.8.1 |
| `slurm` | SUSE:Linux Enterprise Module for HPC 15 SP1 | All versions | 18.08.9-3.13.2 |
| `slurm_20_02` | SUSE:Linux Enterprise Module for HPC 15 SP1 | All versions | 20.02.3-3.8.1 |
| `slurm` | openSUSE:Leap 15.1 | All versions | 18.08.9-lp151.2.1 |
| `slurm` | openSUSE:Leap 15.1 | All versions | 18.08.9-lp151.2.10.1 |
| `slurm` | openSUSE:Leap 15.2 | All versions | 18.08.9-lp152.2.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Opensuse Leap, Schedmd Slurm.

## How do I fix CVE-2020-12693?

Upgrade to a fixed version.

## Is CVE-2020-12693 being exploited?

There is no known exploitation of CVE-2020-12693 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12693 and fix it if it is affected.

What it is: CVE-2020-12693 is a high-severity vulnerability in Debian Debian Linux, published on 21 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12693 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-12693/ (Markdown: https://insights.sbomify.com/CVE-2020-12693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-12693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-12693
- OSV: https://osv.dev/vulnerability/CVE-2020-12693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-12693/
Summaries are generated and may contain mistakes; the official description above is the record.