# CVE-2023-49938: Privilege escalation in n/a

> Attackers can modify extended group lists to access files with unauthorized permissions, requiring an upgrade to Slurm.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2023
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-49938, GHSA-3j4p-qc5m-wqgh, UBUNTU-CVE-2023-49938

## What is CVE-2023-49938?

CVE-2023-49938 is a high-severity vulnerability in n/a, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SchedMD Slurm 22.05.x and 23.02.x. There is Incorrect Access Control: an attacker can modified their extended group list that is used with the sbcast subsystem, and open files with an unauthorized set of extended groups. The fixed versions are 22.05.11 and 23.02.7.

## Which versions are affected by CVE-2023-49938?

It affects 1 product.


Products: Schedmd Slurm.

## How do I fix CVE-2023-49938?

Upgrade to a fixed version.

## Is CVE-2023-49938 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49934](https://insights.sbomify.com/CVE-2023-49934/): SQL injection in n/a (critical 9.8)
- [CVE-2023-49937](https://insights.sbomify.com/CVE-2023-49937/): Use after free in n/a (critical 9.8)
- [CVE-2023-49935](https://insights.sbomify.com/CVE-2023-49935/): Auth bypass in n/a (high 8.8)
- [CVE-2016-10030](https://insights.sbomify.com/CVE-2016-10030/): Path traversal in n/a (high 8.1)
- [CVE-2017-15566](https://insights.sbomify.com/CVE-2017-15566/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49938 and fix it if it is affected.

What it is: CVE-2023-49938 is a high-severity vulnerability in n/a, published on 14 Dec 2023. 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-2023-49938 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-2023-49938/ (Markdown: https://insights.sbomify.com/CVE-2023-49938/index.md)
```

## Sources

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

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