dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2023-50232

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 8.1.33 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 getParams Argument Injection 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 getParams method. The issue results from the lack of proper validation of a user-supplied string before using it to prepare an argument for a system call. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-22028.

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

Inductive Automation Ignition contains an argument injection vulnerability in the getParams method. The flaw results from lack of proper validation of user-supplied input before using it in a system call. An attacker can exploit this by tricking a target user into connecting to a malicious server, allowing arbitrary code execution in the context of the current user.

MitigationImplement strict input validation on all parameters passed to the getParams method before using them in system calls. Consider implementing server-side validation and restricting network connections to trusted servers only.

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.33

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 installed Ignition version
    Access the Ignition Gateway web interface and navigate to the 'About' page, or check the installation directory for version metadata. Alternatively, query the Gateway status endpoint or logs for the build version.
    Affected if The installed version is greater than or equal to 8.1.0 and less than 8.1.33
  2. Identify usage of getParams method
    Search project scripts, Alarm Notification pipelines, or any custom Python/Gateway scripts for calls to the getParams method, particularly where it processes parameters that could originate from external or untrusted sources.
    Affected if The getParams method is being called in any project script, notification pipeline, or handler that processes user-supplied or server-supplied parameters
  3. Inspect client Designer connection settings
    In the Ignition Designer, review the 'Network' or 'General' settings on client startup scripts, vision window event handlers, or any component that initiates outbound connections to external servers.
    Affected if Clients or Designers are configured to automatically connect to or fetch parameters from servers that are not explicitly trusted or are dynamically specified
  4. Review Alarm Notification profiles
    Examine any Alarm Notification settings that use HTTP endpoints, web hooks, or remote notification handlers where the getParams method may be used to process incoming notification parameters.
    Affected if Notification profiles process parameters from external HTTP sources without validation

You are affected if your Ignition version is between 8.1.0 and 8.1.32 (inclusive) AND you use the getParams method in contexts where it processes parameters from external or untrusted server connections.

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.33 or later
Fixed in 8.1.33
Interim mitigation

Implement strict input validation on all parameters passed to the getParams method before using them in system calls. Consider implementing server-side validation and restricting network connections to trusted servers only.

Recommended fix High confidence

Ignition 8.1.33 or later

  1. 1. Create a full backup of the Ignition installation, including the projects folder, gateway backup, and any custom configurations
  2. 2. Download Ignition version 8.1.33 or later from the official Inductive Automation website (inductiveautomation.com) or your licensed customer portal
  3. 3. Stop the Ignition Gateway service on the affected server
  4. 4. Install the updated Ignition version using the installer or by applying the patch, following Inductive Automation's standard upgrade procedure
  5. 5. After installation completes, restart the Ignition Gateway service
  6. 6. Verify the gateway is operational and all projects load correctly
  7. 7. Confirm the getParams method now properly validates user-supplied input

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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