dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2023-39476

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 8.1.35 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 JavaSerializationCodec 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 not required to exploit this vulnerability. The specific flaw exists within the JavaSerializationCodec 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-20291.

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

This is a critical unauthenticated remote code execution vulnerability in Inductive Automation Ignition's JavaSerializationCodec class. The flaw stems from insufficient validation of user-supplied data during deserialization, allowing remote attackers to execute arbitrary code with SYSTEM privileges without any authentication.

MitigationApply the vendor patch from Inductive Automation immediately. Until patched, restrict network exposure of affected Ignition installations and implement network segmentation to limit attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 if Inductive Automation Ignition is installed
    Look for Ignition installation directories or check running services for Ignition processes (typically under C:\Program Files\Inductive Automation\Ignition or /var/lib/ignition on Linux)
    Affected if Ignition software is found on the system
  2. Determine the installed Ignition version
    Check the Ignition installation for version information (typically in a manifest file, about dialog, or gateway status page)
    Affected if The installed version is >= 8.1.0 and < 8.1.35
  3. Verify the JavaSerializationCodec component is present
    Inspect the Ignition installation for the JavaSerializationCodec class or module (typically found in the gateway or core libraries)
    Affected if The JavaSerializationCodec component exists in the installation
  4. Check if the gateway is network-exposed
    Review firewall rules and network configuration to determine if the Ignition gateway port (default 8088/8443) is accessible from untrusted networks
    Affected if The Ignition gateway is reachable from external or untrusted networks without network segmentation
  5. Confirm no authentication is required for the vulnerable endpoint
    Verify the deserialization endpoint configuration to confirm it accepts unauthenticated requests
    Affected if The JavaSerializationCodec endpoint accepts requests without requiring authentication

The environment is affected if Ignition version is 8.1.0 through 8.1.34 and the gateway is network-accessible, since the vulnerability allows unauthenticated remote code execution.

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 from Inductive Automation immediately. Until patched, restrict network exposure of affected Ignition installations and implement network segmentation to limit attack surface.

Recommended fix High confidence

Ignition 8.1.35 or later

  1. Download Ignition version 8.1.35 or later from the official Inductive Automation website (https://inductiveautomation.com/downloads/)
  2. Review Inductive Automation's upgrade documentation and release notes for version 8.1.35
  3. Back up your existing Ignition configuration and projects before upgrading
  4. Deploy the upgrade to your Ignition gateway following standard upgrade procedures
  5. Verify the gateway is operational and all critical functions are working post-upgrade

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

Fix this in Ignition Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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