CVE-2025-37164

HPE OneView Code Injection Exploitation (CVE-2025-37164)

Detects exploitation of CVE-2025-37164, a code injection vulnerability (CWE-94) in Hewlett Packard Enterprise OneView. This vulnerability is listed in the CISA Known Exploited Vulnerabilities catalog and allows attackers to inject and execute arbitrary code through the OneView management platform, potentially compromising datacenter infrastructure management.

Vulnerability Intelligence

KEV — Known Exploited

Affected Software

Vendor
Hewlett Packard Enterprise (HPE)
Product
OneView

Weakness (CWE)

Timeline

Disclosed
January 7, 2026

CVSS

Unscored
Write-up coming soon

What is CVE-2025-37164 HPE OneView Code Injection Exploitation (CVE-2025-37164)?

HPE OneView Code Injection Exploitation (CVE-2025-37164) (CVE-2025-37164) maps to the Initial Access and Execution and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for HPE OneView Code Injection Exploitation (CVE-2025-37164), covering the data sources and telemetry it touches: DeviceNetworkEvents, DeviceProcessEvents, CommonSecurityLog, SecurityEvent. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement
Microsoft Sentinel / Defender
kusto
let OneViewIPs = dynamic([]);
let suspiciousProcesses = dynamic(["bash", "sh", "python", "python3", "perl", "ruby", "curl", "wget", "nc", "ncat", "socat"]);
let lookback = 24h;
union 
  (
    DeviceNetworkEvents
    | where TimeGenerated >= ago(lookback)
    | where RemotePort in (443, 80, 8080, 8443)
    | where RemoteUrl has_any ("oneview", "hpeoneview")
    | project TimeGenerated, DeviceId, DeviceName, InitiatingProcessFileName, RemoteIP, RemoteUrl, RemotePort, ActionType
    | extend AlertSource = "NetworkEvent"
  ),
  (
    DeviceProcessEvents
    | where TimeGenerated >= ago(lookback)
    | where InitiatingProcessFileName =~ "java" or InitiatingProcessParentFileName =~ "java"
    | where FileName in~ (suspiciousProcesses)
    | where InitiatingProcessCommandLine has_any ("oneview", "hpov", "com.hp.ov", "ImageStreamer")
    | project TimeGenerated, DeviceId, DeviceName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, InitiatingProcessFileName
    | extend AlertSource = "ProcessEvent"
  ),
  (
    CommonSecurityLog
    | where TimeGenerated >= ago(lookback)
    | where DeviceProduct has_any ("OneView", "HPE OneView")
    | where Activity has_any ("code injection", "script execution", "command execution", "eval", "exec")
    | project TimeGenerated, DeviceVendor, DeviceProduct, SourceIP, DestinationIP, Activity, Message
    | extend AlertSource = "CommonSecurityLog"
  )
| summarize Count=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by AlertSource, DeviceName, SourceIP=coalesce(RemoteIP, SourceIP)
| where Count > 0
| extend Severity = "High"
| extend CVE = "CVE-2025-37164"

Detects potential exploitation of HPE OneView code injection vulnerability by monitoring for suspicious process spawning from Java processes related to OneView, anomalous network activity to OneView endpoints, and security log events indicating code execution attempts.

critical severity medium confidence

Data Sources

DeviceNetworkEvents DeviceProcessEvents CommonSecurityLog SecurityEvent

Required Tables

DeviceNetworkEvents DeviceProcessEvents CommonSecurityLog

False Positives

  • Legitimate administrative scripts executed by HPE OneView during maintenance or updates
  • Authorized penetration testing activities against OneView infrastructure
  • Automated backup or monitoring tools that spawn child processes from OneView Java services
  • HPE OneView appliance upgrades that execute shell scripts as part of the update process

Sigma rule & cross-platform mapping

The detection logic for HPE OneView Code Injection Exploitation (CVE-2025-37164) (CVE-2025-37164) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1HPE OneView REST API Code Injection Simulation

    Expected signal: HTTP POST request to /rest/login-sessions with injection pattern in request body visible in web access logs; network flow from test host to OneView appliance on port 443

  2. Test 2Simulated Child Process Spawn from Java Context

    Expected signal: Process event showing java parent spawning /bin/bash child process; bash executing id, hostname, whoami commands

  3. Test 3OneView API Reconnaissance — Endpoint Enumeration

    Expected signal: Multiple HTTP GET requests to OneView API endpoints from a single source IP within a short timeframe; mix of 401, 403, and potentially 200 responses visible in access logs

  4. Test 4Reverse Shell Establishment Post-Injection Simulation

    Expected signal: Outbound TCP connection from OneView appliance or compromised host to attacker IP on non-standard port; ncat or bash process with network socket; network flow egress event

Unlock Pro Content

Get the full detection package for CVE-2025-37164 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections