# CVE-2024-49351: IBM Workload Scheduler information disclosure

> Local attackers can read plain-text user credentials stored by IBM Workload Scheduler, leading to potential account compromise.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** No
- **Published:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-gc3f-wwwq-j375

## What is CVE-2024-49351?

CVE-2024-49351 is a medium-severity vulnerability in IBM Workload Scheduler, published on 26 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Workload Scheduler 9.5, 10.1, and 10.2 stores user credentials in plain text which can be read by a local user.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2024-49351?

It affects 1 product.


Products: Ibm Workload Scheduler.

## How do I fix CVE-2024-49351?

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

## Is CVE-2024-49351 being exploited?

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

## Other vulnerabilities in IBM Workload Scheduler

- [CVE-2022-22369](https://insights.sbomify.com/CVE-2022-22369/): Denial of service in Workload Scheduler (medium 6.2)
- [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-2024-49351 and fix it if it is affected.

What it is: CVE-2024-49351 is a medium-severity vulnerability in IBM Workload Scheduler, published on 26 Nov 2024. 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-2024-49351 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-2024-49351/ (Markdown: https://insights.sbomify.com/CVE-2024-49351/index.md)
```

## Sources

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

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