# CVE-2022-29500: Missing authorization in n/a

> Incorrect access control in Slurm allows attackers to disclose sensitive information without proper authorization.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-29500, GHSA-8g6p-72jw-r627, SUSE-RU-2023:4332-1, SUSE-RU-2023:4333-1, SUSE-RU-2023:4334-1, SUSE-RU-2023:4335-1, SUSE-RU-2023:4336-1, UBUNTU-CVE-2022-29500

## What is CVE-2022-29500?

CVE-2022-29500 is a high-severity missing authorization vulnerability in Debian Debian Linux, published on 5 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control that leads to Information Disclosure.

## Which versions are affected by CVE-2022-29500?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 23.02.5-150100.3.11.2 |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 23.02.5-150200.5.11.2 |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 23.02.5-150300.7.11.2 |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 23.02.5-150300.7.11.2 |
| `slurm_23_02` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 23.02.5-3.10.6 |
| `slurm_23_02` | SUSE:Linux Enterprise Module for HPC 15 SP4 | All versions | 23.02.5-150300.7.11.2 |
| `slurm` | SUSE:Linux Enterprise Module for HPC 15 SP5 | All versions | 23.02.5-150500.5.9.2 |
| `slurm` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 23.02.5-150500.5.9.2 |
| `slurm_23_02` | openSUSE:Leap 15.4 | All versions | 23.02.5-150300.7.11.2 |
| `slurm` | openSUSE:Leap 15.5 | All versions | 23.02.5-150500.5.9.2 |

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

## How do I fix CVE-2022-29500?

Apply the vendor's patch.

## Is CVE-2022-29500 being exploited?

There is no known exploitation of CVE-2022-29500 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-2022-29500 and fix it if it is affected.

What it is: CVE-2022-29500 is a high-severity missing authorization vulnerability in Debian Debian Linux, published on 5 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29500 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-2022-29500/ (Markdown: https://insights.sbomify.com/CVE-2022-29500/index.md)
```

## Sources

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

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