Emerson Ovation Insufficient Verification of Data Authenticity
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.0 Feature Pack 3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.8.0 Feature Pack 3.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
CVE-2022-30267 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Ovation; fixed in 3.8.0 Feature Pack 3.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 3.8.0 Feature Pack 3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Emerson Ovation industrial control system software is affected, and it does not properly verify that firmware updates are genuine. An attacker could push malicious firmware, cause a denial-of-service outage, or run code remotely on the system.
Read the original description
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.
What to do
Upgrade to a fixed version: 3.8.0 Feature Pack 3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Emerson Ovation
through Version 3.8.0 Feature Pack 1
Evidence 2
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2022-30267
Is CVE-2022-30267 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw lets data such as firmware images be accepted without proper checks that they are authentic. An attacker could use this to push malicious firmware images, cause a denial-of-service condition, or achieve remote code execution.Source: cisa.gov
Which versions are affected by CVE-2022-30267?
Ovation: through Version 3.8.0 Feature Pack 1.Source: cve.now feed data
Am I affected, and how do I check?
Ovation version 3.8.0 Feature Pack 1 and all earlier versions are listed as affected. To check, look up the Ovation version installed on the system.Source: cisa.gov
How do I fix CVE-2022-30267?
Upgrade to Ovation 3.8.0 Feature Pack 3, which the advisory says remediates many of the identified vulnerabilities.Source: cisa.gov