# CVE-2009-2084: Privilege escalation in n/a

> Local users can gain privileges and modify files due to improper supplementary group settings in SLURM daemons.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1776-1, GHSA-qr6c-5p22-3q9v

## What is CVE-2009-2084?

CVE-2009-2084 is a high-severity vulnerability in n/a, published on 16 Jun 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Simple Linux Utility for Resource Management (SLURM) 1.2 and 1.3 before 1.3.14 does not properly set supplementary groups before invoking (1) sbcast from the slurmd daemon or (2) strigger from the slurmctld daemon, which might allow local SLURM users to modify files and gain privileges.

Weakness: CWE-255

## Which versions are affected by CVE-2009-2084?

It affects 1 product.


Products: Llnl Slurm.

## How do I fix CVE-2009-2084?

Upgrade to a fixed version.

## Is CVE-2009-2084 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3380](https://insights.sbomify.com/CVE-2010-3380/): Privilege escalation in n/a (medium 6.9)
- [CVE-2009-0128](https://insights.sbomify.com/CVE-2009-0128/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2084 and fix it if it is affected.

What it is: CVE-2009-2084 is a high-severity vulnerability in n/a, published on 16 Jun 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2084 in the wild and no public exploit code.

Affected product: n/a. 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-2009-2084/ (Markdown: https://insights.sbomify.com/CVE-2009-2084/index.md)
```

## Sources

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

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