# CVE-2024-41781: IBM PowerVM Hypervisor information disclosure

> An attacker with service access to the HMC can decrypt and read sensitive data from the IBM PowerVM Platform KeyStore.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-g7gv-3436-vxj2

## What is CVE-2024-41781?

CVE-2024-41781 is a medium-severity vulnerability in IBM PowerVM Hypervisor, published on 22 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

IBM PowerVM Platform KeyStore (IBM PowerVM Hypervisor FW950.00 through FW950.90, FW1030.00 through FW1030.60, FW1050.00 through FW1050.20, and FW1060.00 through FW1060.10 functionality can be compromised if an attacker gains service access to the HMC.  An attacker that gains service access to the HMC can locate and through a series of service procedures decrypt data contained in the Platform KeyStore.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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

It affects 1 product.


Products: Ibm Powervm Hypervisor.

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

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

## Is CVE-2024-41781 being exploited?

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

## Other vulnerabilities in IBM PowerVM Hypervisor

- [CVE-2023-30438](https://insights.sbomify.com/CVE-2023-30438/): IBM PowerVM gain access (critical 9.3)
- [CVE-2021-38918](https://insights.sbomify.com/CVE-2021-38918/): Security feature bypass in PowerVM Hypervisor (high 8.6)
- [CVE-2022-22445](https://insights.sbomify.com/CVE-2022-22445/): Privilege escalation in PowerVM Hypervisor (high 7.6)
- [CVE-2021-38917](https://insights.sbomify.com/CVE-2021-38917/): Privilege escalation in PowerVM Hypervisor (high 7.4)
- [CVE-2025-36035](https://insights.sbomify.com/CVE-2025-36035/): IBM PowerVM Hypervisor denial of service (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41781 is a medium-severity vulnerability in IBM PowerVM Hypervisor, published on 22 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-41781 in the wild and no public exploit code.

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

## Sources

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

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