CVE-2022-30267

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qg2p-82g5-qr39 ↗EUVD-2022-56079 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Emerson Ovation >= 0, <= Version 3.8.0 Feature Pack 1
CWE-345 Insufficient Verification of Data Authenticity
ETK-2026-3418Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 58msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h13m
0
+4h
+6h
+8h
+10h
+12h

description

Emerson Ovation firmware verification does not authenticate firmware signatures and uses an insecure integrity check. An attacker with network access may be able to deploy malicious firmware, causing service disruption or code execution.

mitigation

Restrict network access to Ovation firmware update and management interfaces to trusted administrators and isolated management networks. No fixed version is recorded; obtain and apply Emerson guidance or updates when available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 23:03Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-03 23:03Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2022-30267

{
  "etk_id": "ETK-2026-3418",
  "cve_id": "CVE-2022-30267",
  "display_id": "CVE-2022-30267",
  "ghsa_id": "GHSA-qg2p-82g5-qr39",
  "euvd_id": "EUVD-2022-56079",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated firmware verification in Emerson Ovation",
  "summary": "Emerson Ovation firmware verification does not authenticate firmware signatures and uses an insecure integrity check. An attacker with network access may be able to deploy malicious firmware, causing service disruption or code execution.",
  "mitigation": "Restrict network access to Ovation firmware update and management interfaces to trusted administrators and isolated management networks. No fixed version is recorded; obtain and apply Emerson guidance or updates when available.",
  "vendor": "Emerson",
  "product": "Ovation",
  "affected": [
    {
      "affected_notes": [
        ">= 0, <= Version 3.8.0 Feature Pack 1"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Ovation",
      "purl": null
    }
  ],
  "cwes": [
    345
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.1485085,
  "t0_at": "2026-11-03T23:03:12.532000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T23:03:12.532000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T23:03:12.532000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2022-30267"
    }
  }
}

published 2026-11-03 23:39Z
last change 2026-11-04 04:08Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.