# CVE-2024-22341: IBM Watson Query on Cloud Pak for Data information disclosure

> Unauthorized users can access remote data source objects in IBM Watson Query due to improper privilege management, requiring a patch.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-c9vm-r7mj-wm49

## What is CVE-2024-22341?

CVE-2024-22341 is a medium-severity missing authorization vulnerability in IBM Watson Query on Cloud Pak for Data, published on 22 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Watson Query on Cloud Pak for Data 4.0.0 through 4.0.9, 4.5.0 through 4.5.3, 4.6.0 through 4.6.6, 4.7.0 through 4.7.4, and 4.8.0 through 4.8.7 could allow unauthorized data access from a remote data source object due to improper privilege management.

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Ibm Watson Query With Cloud Pak for Data.

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

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

## Is CVE-2024-22341 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22341 and fix it if it is affected.

What it is: CVE-2024-22341 is a medium-severity missing authorization vulnerability in IBM Watson Query on Cloud Pak for Data, published on 22 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22341 in the wild and no public exploit code.

Affected product: IBM Watson Query 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-2024-22341/ (Markdown: https://insights.sbomify.com/CVE-2024-22341/index.md)
```

## Sources

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

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