Live › vulnerability › CVE-2022-30267
Emerson Ovation does not authenticate firmware signing and relies on an insecure checksum for integrity, so an attacker who can reach it over the network could push a malicious firmware image to cause denial of service or remote code execution. Reported by Forescout (OT:ICEFALL). CISA reports no known public exploitation.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 23:45 UTC. All times on this page are UTC.
Organizations running Emerson Ovation control systems, mostly in the energy sector, on version 3.8.0 Feature Pack 1 or earlier. Exposure depends on whether an attacker can reach the controllers over the network. Teams that don't run Ovation, or whose control networks are isolated from business networks and the internet, are at much lower risk.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Ovation | vendor | <= 3.8.0 Feature Pack 1 | 3.8.0 Feature Pack 3 |
3.8.0 Feature Pack 1 or earlier is affecteds guidance is in manual OVREF1000 (Ovation Users Group login required); questions go to Ovation-CERT, 1-800-445-9723 option 33.8.0 Feature Pack 3, described as remediating many of the identified vulnerabilities; the advisory does not name this CVE specifically, so confirm with Ovation-CERTEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Emerson Ovation was found to have no authentication of firmware signing and relies on an insecure checksum for integrity. This could allow an attacker to push malicious firmware images, cause a denial-of-service condition, or achieve remote code execution.
This page as .md · .json · in your agent: get_signal("CVE-2022-30267")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.