dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2023-39473

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 8.1.35 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click

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
Inductive Automation Ignition AbstractGatewayFunction Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition. Authentication is required to exploit this vulnerability. The specific flaw exists within the AbstractGatewayFunction class. 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-17587.

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

The vulnerability exists in Inductive Automation Ignition's AbstractGatewayFunction class, where insufficient validation of user-supplied data allows deserialization of untrusted data. An authenticated attacker can exploit this to achieve remote code execution with SYSTEM privileges.

MitigationApply vendor-supplied patches for Ignition and implement strict input validation on all gateway functions to prevent deserialization of untrusted data. Consider network segmentation to limit access to the gateway interface.

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.0, < 8.1.35

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Check Ignition version
    Access the Ignition Gateway status page or use the gateway's built-in version check command to determine the installed version number.
    Affected if The installed version is 8.1.0 or higher but lower than 8.1.35.
  2. Verify Gateway API exposure
    Inspect network configuration to determine if the Ignition Gateway web interface/API is accessible from untrusted networks. Check firewall rules and gateway network bindings.
    Affected if The Gateway interface is exposed to network segments that contain untrusted or attacker-accessible systems.
  3. Confirm Gateway authentication status
    Review the Ignition Gateway security settings to verify whether authentication is enabled for gateway functions and API access.
    Affected if Authentication is disabled or weak authentication is configured, allowing unauthenticated or low-privilege access to gateway functions.
  4. Identify exposed AbstractGatewayFunction endpoints
    Review the Gateway's deployed modules and configured web endpoints to identify any custom or third-party gateway functions that use the AbstractGatewayFunction class.
    Affected if Custom or third-party modules exposing Gateway functions are installed and accessible without additional validation controls.

The environment is affected if Ignition version is 8.1.0 through 8.1.34 AND the Gateway interface or its functions are accessible to authenticated users who could supply untrusted serialized data.

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
Upgrade available Upgrade to 8.1.35 or later
Fixed in 8.1.35
Interim mitigation

Apply vendor-supplied patches for Ignition and implement strict input validation on all gateway functions to prevent deserialization of untrusted data. Consider network segmentation to limit access to the gateway interface.

Recommended fix High confidence

Ignition 8.1.35 or later

  1. 1. Check current Ignition version by accessing the Gateway Status page or checking the startup logs
  2. 2. Create a complete backup of the Ignition gateway, including the project files and database if applicable
  3. 3. Download Ignition version 8.1.35 or later from the Inductive Automation website
  4. 4. Stop the Ignition Gateway service before upgrading
  5. 5. Run the installer or use the built-in upgrade mechanism to upgrade to version 8.1.35
  6. 6. Start the Ignition Gateway service after upgrade completes
  7. 7. Verify the upgrade was successful by checking the Gateway version in the Gateway Status page
  8. 8. Test critical applications and workflows to ensure functionality is intact
Caveat Review Inductive Automation release notes for 8.1.35 for any specific configuration or feature changes before upgrading

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

Fix this in Ignition Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39473 — 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-2023-39473 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