IBM PowerVM Hypervisor up to FW950.90/FW1030.60/FW1050.20/FW1060.10 HMC information expsure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in IBM PowerVM Hypervisor up to FW950.90/FW1030.60/FW1050.20/FW1060.10. This issue affects some unknown processing of the component HMC. The manipulation leads to information expsure. This vulnerability is traded as CVE-2024-41781. Access to the local network is required for this attack to succeed. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in IBM PowerVM Hypervisor up to FW950.90/FW1030.60/FW1050.20/FW1060.10. It has been rated as problematic. This issue affects an unknown functionality of the component HMC. The manipulation with an unknown input leads to a information expsure vulnerability. Using CWE to declare the problem leads to CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. Impacted is confidentiality. The summary by CVE is:
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.
It is possible to read the advisory at ibm.com. The identification of this vulnerability is CVE-2024-41781 since 07/22/2024. The exploitation is known to be difficult. The attack can only be done within the local network. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
- FW950.0
- FW950.1
- FW950.2
- FW950.3
- FW950.4
- FW950.5
- FW950.6
- FW950.7
- FW950.8
- FW950.9
- FW950.10
- FW950.11
- FW950.12
- FW950.13
- FW950.14
- FW950.15
- FW950.16
- FW950.17
- FW950.18
- FW950.19
- FW950.20
- FW950.21
- FW950.22
- FW950.23
- FW950.24
- FW950.25
- FW950.26
- FW950.27
- FW950.28
- FW950.29
- FW950.30
- FW950.31
- FW950.32
- FW950.33
- FW950.34
- FW950.35
- FW950.36
- FW950.37
- FW950.38
- FW950.39
- FW950.40
- FW950.41
- FW950.42
- FW950.43
- FW950.44
- FW950.45
- FW950.46
- FW950.47
- FW950.48
- FW950.49
- FW950.50
- FW950.51
- FW950.52
- FW950.53
- FW950.54
- FW950.55
- FW950.56
- FW950.57
- FW950.58
- FW950.59
- FW950.60
- FW950.61
- FW950.62
- FW950.63
- FW950.64
- FW950.65
- FW950.66
- FW950.67
- FW950.68
- FW950.69
- FW950.70
- FW950.71
- FW950.72
- FW950.73
- FW950.74
- FW950.75
- FW950.76
- FW950.77
- FW950.78
- FW950.79
- FW950.80
- FW950.81
- FW950.82
- FW950.83
- FW950.84
- FW950.85
- FW950.86
- FW950.87
- FW950.88
- FW950.89
- FW950.90
- FW1030.0
- FW1030.1
- FW1030.2
- FW1030.3
- FW1030.4
- FW1030.5
- FW1030.6
- FW1030.7
- FW1030.8
- FW1030.9
- FW1030.10
- FW1030.11
- FW1030.12
- FW1030.13
- FW1030.14
- FW1030.15
- FW1030.16
- FW1030.17
- FW1030.18
- FW1030.19
- FW1030.20
- FW1030.21
- FW1030.22
- FW1030.23
- FW1030.24
- FW1030.25
- FW1030.26
- FW1030.27
- FW1030.28
- FW1030.29
- FW1030.30
- FW1030.31
- FW1030.32
- FW1030.33
- FW1030.34
- FW1030.35
- FW1030.36
- FW1030.37
- FW1030.38
- FW1030.39
- FW1030.40
- FW1030.41
- FW1030.42
- FW1030.43
- FW1030.44
- FW1030.45
- FW1030.46
- FW1030.47
- FW1030.48
- FW1030.49
- FW1030.50
- FW1030.51
- FW1030.52
- FW1030.53
- FW1030.54
- FW1030.55
- FW1030.56
- FW1030.57
- FW1030.58
- FW1030.59
- FW1030.60
- FW1050.0
- FW1050.1
- FW1050.2
- FW1050.3
- FW1050.4
- FW1050.5
- FW1050.6
- FW1050.7
- FW1050.8
- FW1050.9
- FW1050.10
- FW1050.11
- FW1050.12
- FW1050.13
- FW1050.14
- FW1050.15
- FW1050.16
- FW1050.17
- FW1050.18
- FW1050.19
- FW1050.20
- FW1060.0
- FW1060.1
- FW1060.2
- FW1060.3
- FW1060.4
- FW1060.5
- FW1060.6
- FW1060.7
- FW1060.8
- FW1060.9
- FW1060.10
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 1.8
VulDB Temp Score: 1.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CNA Base Score: 5.1
CNA Vector (ibm): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information expsureCWE: CWE-497
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
07/22/2024 🔍11/22/2024 🔍
11/22/2024 🔍
08/15/2025 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Confirmed
CVE: CVE-2024-41781 (🔍)
GCVE (CVE): GCVE-0-2024-41781
GCVE (VulDB): GCVE-100-285839
Entry
Created: 11/22/2024 13:52Updated: 08/15/2025 19:56
Changes: 11/22/2024 13:52 (63), 02/23/2025 13:58 (3), 08/15/2025 19:56 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.