dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2022-35870

HIGH · 7.8 CVSS v3.1 Published 2022-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition 8.1.15 (b2022030114). Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within com.inductiveautomation.metro.impl. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-17265.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A deserialization vulnerability in com.inductiveautomation.metro.impl in Inductive Automation Ignition 8.1.15 allows remote attackers to bypass authentication and execute arbitrary code as SYSTEM via deserialization of untrusted user-supplied data.

MitigationApply the vendor patch or update to a fixed version of Ignition 8.1.x that addresses this deserialization flaw and the authentication bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IgnitionApplication
Affected:= 8.1.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Ignition version
    Check the Ignition installation directory for version information, or query the gateway via the status page or launcher's about dialog
    Affected if the installed version is exactly 8.1.15 (the affected version)
  2. Locate the metro.impl component
    Inspect the Ignition installation lib folder or gateway backup for com.inductiveautomation.metro.impl JAR file presence
    Affected if the metro.impl component is present in the installation
  3. Assess network exposure of the gateway
    Review network configuration to determine if the Ignition gateway web port is accessible from untrusted networks
    Affected if the gateway HTTP/HTTPS ports are exposed to untrusted or public networks, allowing untrusted user-supplied data to reach the affected component
  4. Check for custom deserialization configurations
    Review any custom Python or Java serialization configurations in the ignition.gateway or custom module settings
    Affected if custom serializers or unsafe deserialization settings are configured that could accept untrusted data

You are affected if the installed Ignition version is exactly 8.1.15 and the gateway is network-accessible to accept untrusted user-supplied data that could reach the metro.impl component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or update to a fixed version of Ignition 8.1.x that addresses this deserialization flaw and the authentication bypass.

Recommended fix Moderate confidence

Ignition 8.1.16 or later (latest 8.1.x stable release)

  1. 1. Navigate to the Inductive Automation download portal at support.inductiveautomation.com
  2. 2. Download the latest Ignition 8.1.x release (newer than 8.1.15) which contains the security fix for this deserialization vulnerability
  3. 3. Back up your current Ignition installation and project data
  4. 4. Install the updated version following standard Inductive Automation upgrade procedures
  5. 5. Verify the gateway is operational after upgrade
Caveat Review release notes for any breaking changes between 8.1.15 and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ignition Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35870 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data