dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2023-39474

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 →
95/100
Remediation priority · Urgent
Remotely reachable 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
Inductive Automation Ignition downloadLaunchClientJar Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition. User interaction is required to exploit this vulnerability in that the target must connect to a malicious server. The specific flaw exists within the downloadLaunchClientJar function. The issue results from the lack of validating a remote JAR file prior to loading it. An attacker can leverage this vulnerability to execute code in the context of the current user. . Was ZDI-CAN-19915.

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 the downloadLaunchClientJar function of Inductive Automation Ignition. The application fails to validate or verify remote JAR files before loading them, allowing an attacker serving a malicious JAR to achieve code execution in the context of the current user. Exploitation requires the target user to connect to a malicious server.

MitigationImplement cryptographic signature validation for all remote JAR files before loading, combined with an allowlist of trusted JAR sources and proper certificate chain verification.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Check Ignition Gateway version
    Log into the Ignition Gateway web interface and look at the status page, or check the installation directory for version information. On Windows, this may also be visible in 'Programs and Features'.
    Affected if The installed version is 8.1.0 through 8.1.34 (versions below 8.1.35)
  2. Identify if remote client launcher JAR downloads are configured
    In the Gateway, navigate to the Client Launch settings (Configure > Client > Launch). Look for any configuration allowing remote JAR URL sources or custom launch URLs pointing to external servers.
    Affected if The Gateway is configured to download the client launcher JAR from a remote/untrusted server, or allows clients to specify custom JAR URLs
  3. Review network configuration for client connections
    Check the Gateway network settings and see if there are any allowlist or blocklist controls for where clients can download JAR files from. Look for any configured remote launch endpoints.
    Affected if There are no restrictions on remote JAR sources and the launch configuration permits fetching JARs from external URLs

You are affected if the Ignition Gateway version is 8.1.0 through 8.1.34 AND the system is configured to allow remote JAR file downloads for client launching.

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

Implement cryptographic signature validation for all remote JAR files before loading, combined with an allowlist of trusted JAR sources and proper certificate chain verification.

Recommended fix High confidence

8.1.35

  1. Schedule a maintenance window for the Ignition upgrade
  2. Back up the Ignition Gateway configuration and any custom modules
  3. Download Inductive Automation Ignition version 8.1.35 or later from the official vendor site
  4. Stop the Ignition Gateway service
  5. Install the version 8.1.35 upgrade following vendor documentation
  6. Start the Ignition Gateway service
  7. Verify the Gateway is operational and all critical functions are working

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

Fix this in Ignition Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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