HPE OneView for VMware vCenter (OV4VC), स्थानीय विशेषाधिकार वृद्धि

The impact of CVE-2025-37101 is significant due to the potential for vertical privilege escalation. An attacker who initially gains read-only access to the system could exploit this vulnerability to gain administrative privileges. This could allow them to modify system configurations, access sensitive data, and potentially compromise the entire environment. The ability to perform admin actions from a read-only account circumvents standard security controls and represents a serious escalation of risk. This vulnerability shares similarities with other privilege escalation exploits where seemingly limited access is leveraged to gain broader control.

Organizations utilizing HPE OneView for VMware vCenter, particularly those with deployments where read-only accounts are granted broad access to system resources, are at significant risk. Shared hosting environments where multiple tenants share the same OneView instance are also particularly vulnerable, as a compromise of one tenant's read-only account could lead to broader system compromise.

• hpe / server:

Get-WinEvent -LogName Security -Filter "EventID=4624 -Message contains 'OneView'" | Where-Object {$_.Properties[0].Value -match 'Read-Only'}

• hpe / server:

Get-Process | Where-Object {$_.ProcessName -match 'OneView'}

• generic web:

curl -I https://<oneview_server>/admin/ | grep 'Server: HPE OneView' # Check for admin endpoint exposure

1. 2025-06-26Disclosure

   disclosure

1. आरक्षित2025-04-16
2. प्रकाशित2025-06-26
3. संशोधित2026-02-26
4. EPSS अद्यतन2026-03-23

The primary mitigation for CVE-2025-37101 is to upgrade HPE OneView for VMware vCenter to version 11.7 or later, which contains the fix. If an immediate upgrade is not feasible, consider implementing stricter access controls to limit the scope of read-only accounts. Review existing user permissions and ensure the principle of least privilege is enforced. Monitor system logs for any unusual activity or attempts to escalate privileges. While a direct WAF rule is unlikely, consider implementing general rules to detect and block suspicious privilege escalation attempts.