dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2023-50223

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 ExtendedDocumentCodec 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 ExtendedDocumentCodec 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-22127.

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 · moderate confidence

The vulnerability exists in Inductive Automation Ignition's ExtendedDocumentCodec class, where improper validation of user-supplied data allows deserialization of untrusted data. An authenticated attacker can exploit this to achieve remote code execution with SYSTEM privileges, leveraging the deserialization attack vector to inject malicious serialized objects.

MitigationApply the vendor patch for CVE-2023-50223 when released, and ensure network access to Ignition is restricted to authenticated users only. Review deserialization allowlists if the platform supports them.

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. Identify installed Ignition version
    Check the Ignition Gateway status page, or inspect the installation manifest/version file typically found in the Ignition installation directory. On Windows this may be in the program files folder, on Linux typically under /opt/ignition. The version is also visible on the Gateway web interface login page.
    Affected if The installed version is 8.1.0 or higher but below 8.1.35
  2. Confirm ExtendedDocumentCodec is accessible
    Determine if the Gateway web interface or associated API endpoints are reachable over the network. The vulnerability requires network access to the Ignition Gateway to send malicious serialized data.
    Affected if The Gateway web interface is exposed to network access without proper authentication restrictions
  3. Verify authentication is required for the affected endpoint
    Review network accessibility and authentication configuration for the Ignition Gateway. The vulnerability requires an authenticated session to exploit, but any authenticated user can potentially trigger the deserialization vector.
    Affected if The Gateway allows unauthenticated network access or accepts connections from untrusted users

You are affected if your Ignition installation version is 8.1.0 or higher but below 8.1.35 AND the Gateway is network-accessible to users who are not explicitly trusted.

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 the vendor patch for CVE-2023-50223 when released, and ensure network access to Ignition is restricted to authenticated users only. Review deserialization allowlists if the platform supports them.

Recommended fix High confidence

Ignition 8.1.35 or later

  1. 1. Backup the current Ignition installation and all critical configuration data
  2. 2. Download Ignition version 8.1.35 or later from the official Inductive Automation website (inductiveautomation.com)
  3. 3. Stop the Ignition Gateway service
  4. 4. Run the installer for the new version, following the standard upgrade procedure
  5. 5. Restart the Ignition Gateway service
  6. 6. Verify the upgrade was successful by checking the version number in the Gateway Status page under Configuration > System > Gateway Settings
Caveat Review the Ignition 8.1.35 release notes for any configuration or compatibility 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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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