HomeVulnerabilityCISA flags max-severity bug in HPE OneView amid energetic exploitation

CISA flags max-severity bug in HPE OneView amid energetic exploitation

Infrastructure-wide penalties

CVE-2025-37164 is brought on by improper enter dealing with in a publicly reachable REST API utilized by HPE OneView, permitting unauthenticated attackers to execute arbitrary instructions on the underlying system. The flaw carries a CVSS rating of 10.0, reflecting each the dearth of authentication and the direct path to distant code execution, which makes opportunistic scanning and speedy exploitation way more probably.

HPE OneView acts as a single pane of glass for servers, storage, and networking, usually built-in with identification programs, ticketing platforms, and automation workflows. An unauthenticated RCE in that layer offers attackers a shortcut straight into the guts of enterprise operations.

“HPW OneView’s place within the firm and the vulnerability’s severity rating make it dangerous,” Randolph Barr, chief data security officer at Cequence Safety. “When hackers breach a platform akin to HPE OneView, they not solely acquire entry to a single system but additionally penetrate the core operations of the setting.”

Not an ‘apply and transfer on’ answer

Whereas CISA’s KEV inclusion raised the precedence instantly, enterprises can’t deal with OneView like a routine endpoint patch. Administration-plane software program is usually deployed on-premises, generally on bodily servers, and tightly coupled with manufacturing workflows. A rushed repair that breaks monitoring, authentication, or integrations might be nearly as harmful because the vulnerability itself.

See also  Quicker Patching Tempo Validates CISA's KEV Catalog Initiative

Barr cautioned that organizations first want to grasp how OneView is deployed: whether or not on bodily {hardware}, as a digital machine with snapshot help, or in a clustered configuration, earlier than shifting to patch. Virtualized setups might permit faster patch-and-rollback cycles, whereas older or massive on-prem deployments demand cautious sequencing and examined backout plans.

“Safety groups ought to be amassing risk intelligence on the identical time that they’re creating patching methods,” he stated. “Meaning realizing how the exploit is being utilized, which industries are being focused, whether or not attackers are scanning for susceptible APIs in massive numbers, and what indicators or actions could also be watched all through the patching time.”

- Advertisment -spot_img
RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -

Most Popular