Ignition Security Exploit Advisory

I received an alert from our IT department, US-CERT email.Here is the link.


Has this been addressed with the latest version 8.0.11?
Is V7 affected at all?



  • CVSS v3 9.1
  • ATTENTION: Exploitable remotely/low skill level to exploit
  • Vendor: Inductive Automation
  • Equipment: Ignition 8 Gateway
  • Vulnerability: Improper Access Control


Successful exploitation of this vulnerability could allow an attacker to write endless log statements into the database, which could result in a denial-of-service condition.



The following versions of Ignition 8 Gateway are affected if running the Perspective Module:

  • Ignition 8 Gateway versions prior to 8.0.10



An unprotected logging route may allow an attacker to write endless log statements into the database without space limits or authentication. This results in consuming the entire available hard-disk space, causing a denial-of-service condition.

CVE-2020-10641 has been assigned to this vulnerability. A CVSS v3 base score of 9.1 has been calculated; the CVSS vector string is (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).


  • CRITICAL INFRASTRUCTURE SECTORS: Critical Manufacturing, Energy, Information Technology


Sharon Brizinov and Mashav Sapir from Claroty reported this vulnerability to Inductive Automation and CISA.


Inductive Automation recommends the following mitigation:

  • Upgrade Ignition 8 Gateway to v8.0.10

The following workarounds are suggested if users cannot upgrade to v8.0.10 or above:

  • If running the Perspective Module, set “perspective.routes” to a priority level of WARN or higher. The exploit triggers the code path that logs a message with priority level INFO.
  • For gateways that are deployed behind a web application firewall or reverse proxy, deploy a rule to deny access to all gateway HTTP requests that include the path: /data/perspective/print-to-log.

CISA recommends users take defensive measures to minimize the risk of exploitation of this vulnerability. Specifically, users should:

  • Minimize network exposure for all control system devices and/or systems, and ensure that they are not accessible from the Internet.
  • Locate control system networks and remote devices behind firewalls, and isolate them from the business network.
  • When remote access is required, use secure methods, such as Virtual Private Networks (VPNs), recognizing that VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize that VPN is only as secure as the connected devices.

CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.

CISA also provides a section for control systems security recommended practices on the ICS webpage on us-cert.gov. Several recommended practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.

Additional mitigation guidance and recommended practices are publicly available on the ICS webpage on us-cert.gov in the Technical Information Paper, ICS-TIP-12-146-01B–Targeted Cyber Intrusion Detection and Mitigation Strategies.

Organizations observing any suspected malicious activity should follow their established internal procedures and report their findings to CISA for tracking and correlation against other incidents.

No known public exploits specifically target this vulnerability.

Contact Information

For any questions related to this report, please contact the CISA at:

Email: CISAservicedesk@cisa.dhs.gov
Toll Free: 1-888-282-0870

For industrial control systems cybersecurity information: https://www.us-cert.gov/ics
or incident reporting: https://www.us-cert.gov/report

CISA continuously strives to improve its products and services. You can help by choosing one of the links below to provide feedback about this product.

Yes, and no, in that order; the ‘Affected Products’ section of the report is accurate:

1 Like

That’s what I thought but wanted to get verification.


This could also be mitigated, along with all similar attacks, by setting wrapper.logfile.maxsize= to a non-zero value in wrapper.conf.

When the maxsize is set to a non-zero value does that mean the log file just stops being appended to or is the oldest event removed like a circular buffer?

Also what is the units on that value. Is it max number of logged events or a size in bytes?


The max size is already set and there are comments explaining the values a bit:

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
1 Like

The sqlite db that holds log entries also rolls over by default and does not grow unbounded in size. I’m not sure this advisory was completely accurate. It would let an unauthenticated attacker fill/spam your logs, but I don’t think there was ever a risk of filling the HD unless you had configured your logs to be unbounded in size.

edit: the way rollover is implemented for the logs that go into the DB actually does leave a window where there’s a real risk of filling the HD. So the advisory is not as inaccurate as I thought.