CVE-2022-35870: (Pwn2Own) Inductive Automation Ignition Deserialization of Untrusted Data Remote Code Execution Vulnerability

Published Jul 25, 2022
·
Updated

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.

Other sources

This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition. 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.

ZDI

Affected Software

2 affected components
inductiveautomation Ignition=8.1.15
Inductive Automation Ignition

Event History

Jul 25, 2022
CVE Published
via MITRE·06:16 PM
Data Sourced
via MITRE·06:16 PM
DescriptionSeverityWeakness
Mar 28, 2025
Advisory Published
via ZDI·02:08 AM

Frequently Asked Questions

1

What is CVE-2022-35870 vulnerability?

(Pwn2Own) Inductive Automation Ignition Deserialization of Untrusted Data Remote Code Execution Vulnerability.

2

How severe is CVE-2022-35870?

CVE-2022-35870 has a severity keyword of 'high' with a CVSS score of 8.8.

3

What software versions are affected by CVE-2022-35870?

Inductive Automation Ignition 8.1.15 (b2022030114) is affected by CVE-2022-35870.

4

Is authentication required to exploit CVE-2022-35870?

Authentication is required to exploit CVE-2022-35870, but the existing mechanism can be bypassed.

5

How can I fix CVE-2022-35870 vulnerability?

To address CVE-2022-35870, it is recommended to apply the patches provided by the vendor and follow their security advisory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203