# CVE-2022-38714: IBM DataStage on Cloud Pak for Data information disclosure

> Privileged users can read sensitive credentials stored by IBM DataStage on Cloud Pak for Data, leading to information disclosure.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2024
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-cvhf-7v5m-4vj9

## What is CVE-2022-38714?

CVE-2022-38714 is a medium-severity vulnerability in IBM DataStage on Cloud Pak for Data, published on 12 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM DataStage on Cloud Pak for Data 4.0.6 to 4.5.2 stores sensitive credential information that can be read by a privileged user.  IBM X-Force ID:  235060.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Ibm Datastage.

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

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

## Is CVE-2022-38714 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38714 is a medium-severity vulnerability in IBM DataStage on Cloud Pak for Data, published on 12 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38714 in the wild and no public exploit code.

Affected product: IBM DataStage on Cloud Pak for Data. 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-38714/ (Markdown: https://insights.sbomify.com/CVE-2022-38714/index.md)
```

## Sources

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

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