# CVE-2022-22369: Denial of service in Workload Scheduler

> A local user can overwrite key system files in IBM Workload Scheduler, causing the system to crash and resulting in a denial of service.

- **Severity:** Medium 6.2 (`CVSS:3.0/I:N/S:U/PR:N/A:H/AV:L/UI:N/C:N/AC:L/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h7mp-gpw2-qcgf

## What is CVE-2022-22369?

CVE-2022-22369 is a medium-severity denial of service vulnerability in IBM Workload Scheduler, published on 10 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Workload Scheduler 9.4 and 9.5 could allow a local user to overwrite key system files which would cause the system to crash. IBM X-Force ID: 221187.

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

It affects 1 product.


Products: Ibm Workload Scheduler.

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

No fix has been published for CVE-2022-22369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22369 being exploited?

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

## Other vulnerabilities in IBM Workload Scheduler

- [CVE-2024-49351](https://insights.sbomify.com/CVE-2024-49351/): IBM Workload Scheduler information disclosure (medium 5.5)
- [CVE-2020-4380](https://insights.sbomify.com/CVE-2020-4380/): Cross-site scripting in Workload Scheduler (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22369 and fix it if it is affected.

What it is: CVE-2022-22369 is a medium-severity denial of service vulnerability in IBM Workload Scheduler, published on 10 Aug 2022. 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-2022-22369 in the wild and no public exploit code.

Affected product: IBM Workload Scheduler. 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-22369/ (Markdown: https://insights.sbomify.com/CVE-2022-22369/index.md)
```

## Sources

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

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