IgnitionApplication · Inductiveautomation

CVE-2022-35869

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
This vulnerability allows remote attackers to bypass authentication on affected installations of Inductive Automation Ignition 8.1.15 (b2022030114). Authentication is not required to exploit this vulnerability. The specific flaw exists within com.inductiveautomation.ignition.gateway.web.pages. The issue results from the lack of proper authentication prior to access to functionality. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-17211.

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 an authentication bypass vulnerability in Inductive Automation Ignition 8.1.15 (build b2022030114). The flaw exists in the com.inductiveautomation.ignition.gateway.web.pages component, where proper authentication is not enforced before accessing certain functionality. Remote attackers can exploit this without any credentials to gain unauthorized access to the system.

MitigationApply the vendor security patch for Ignition 8.1.15 immediately. If patching is not immediately possible, restrict network access to the gateway web interface using firewall rules or VPN access until the patch can be applied.

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

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 installed Ignition version
    Access the Ignition Gateway web interface and navigate to the Status page, or check the installation directory for version information files. Look for the exact build number displayed in the gateway.
    Affected if The installed version is Ignition 8.1.15 with build b2022030114 specifically.
  2. Confirm gateway web interface is running
    Attempt to access the Ignition Gateway login page by navigating to the gateway URL on port 8088 (default HTTP) or port 8043 (default HTTPS).
    Affected if The gateway web interface is accessible and responds.
  3. Check network accessibility of web interface
    Determine if the gateway web port is exposed to untrusted networks by reviewing firewall rules, checking bind addresses in gateway configuration, or scanning external-facing IP addresses.
    Affected if The gateway web interface is reachable from untrusted network segments or the public internet.
  4. Verify authentication enforcement
    Attempt to access protected Ignition web resources (such as /main/web/status or other gateway endpoints) directly without providing credentials. Observe whether the system redirects to a login page or permits access.
    Affected if Unauthenticated access to gateway web pages is permitted without redirection to login.

A user is affected if they are running Ignition 8.1.15 (build b2022030114) and the gateway web interface is network-accessible, allowing unauthenticated access to certain web page functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor security patch for Ignition 8.1.15 immediately. If patching is not immediately possible, restrict network access to the gateway web interface using firewall rules or VPN access until the patch can be applied.

Fix this in Ignition Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2022-35869 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