OSIsoft has workarounds and defensive measures in place to handle multiple vulnerabilities in its PI System, according to a report with CISA.
The vulnerabilities are uncontrolled search path element, Improper verification of cryptographic signature, incorrect default permissions, uncaught exception, null pointer dereference, improper input validation, cross-site scripting, and insertion of sensitive information into log file.
Successful exploitation of these remotely exploitable vulnerabilities, discovered by William Knowles, senior security consultant at Applied Risk, could allow an attacker to access unauthorized information, delete or modify local processes, and crash the affected device.
The following versions of PI System are affected: For CVE-2020-10610, CVE-2020-10608, CVE-2020-10606:
- Applications using PI Asset Framework (AF) Client versions prior to and including PI AF Client 2018 SP3 Patch 1, Version 2.10.7.283
- Applications using PI Software Development Kit (SDK) versions prior to and including PI SDK 2018 SP1, Version 1.4.7.602
- PI API for Windows Integrated Security versions prior to and including 2.0.2.5
- PI API versions prior to and including 1.6.8.26
- PI Buffer Subsystem versions prior to and including 4.8.0.18
- PI Connector for BACnet, versions prior to and including 1.2.0.6
- PI Connector for CygNet, versions prior to and including 1.4.0.17
- PI Connector for DC Systems RTscada, versions prior to and including 1.2.0.42
- PI Connector for Ethernet/IP, versions prior to and including 1.1.0.10
- PI Connector for HART-IP, versions prior to and including 1.3.0.1
- PI Connector for Ping, versions prior to and including 1.0.0.54
- PI Connector for Wonderware Historian, versions prior to and including 1.5.0.88
- PI Connector Relay, versions prior to and including 2.5.19.0
- PI Data Archive versions prior to and including PI Data Archive 2018 SP3, Version 3.4.430.460
- PI Data Collection Manager, versions prior to and including 2.5.19.0
- PI Integrator for Business Analytics versions prior to and including 2018 R2 SP1, Version 2.2.0.183
- PI Interface Configuration Utility (ICU) versions prior to and including 1.5.0.7
- PI to OCS versions prior to and including 1.1.36.0
- CVE-2020-10604, CVE-2020-10602
- PI Data Archive 2018 and 2018 SP2 only
CVE-2020-10600:
- PI Data Archive 2018 SP2 and prior versions
CVE-2019-10768:
- PI Vision 2019 and prior
- PI Manual Logger 2017 R2 Patch 1 and prior
- RtReports Version 4.1 and prior
CVE-2020-10600, CVE-2020-10614, CVE-2019-18244:
- PI Vision 2019 and prior versions
In one vulnerability, a local attacker can modify a search path and plant a binary to exploit the affected PI System software to take control of the local computer at Windows system privilege level, resulting in unauthorized information disclosure, deletion, or modification.
CVE-2020-10610 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
In addition, a local attacker can plant a binary and bypass a code integrity check for loading PI System libraries. This exploitation can target another local user of PI System software on the computer to escalate privilege and result in unauthorized information disclosure, deletion, or modification.
CVE-2020-10608 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
Also, a local attacker can exploit incorrect permissions set by affected PI System software. This exploitation can result in unauthorized information disclosure, deletion, or modification if the local computer also processes PI System data from other users, such as from a shared workstation or terminal server deployment.
CVE-2020-10606 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
In another issue, a remote, unauthenticated attacker could crash PI Network Manager service through specially crafted requests. This can result in blocking connections and queries to PI Data Archive.
CVE-2020-10604 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
In addition, an authenticated remote attacker could crash PI Network Manager due to a race condition. This can result in blocking connections and queries to PI Data Archive.
CVE-2020-10602 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.5.
Also, an authenticated remote attacker could crash PI Archive Subsystem when the subsystem is working under memory pressure. This can result in blocking queries to PI Data Archive.
CVE-2020-10600 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.9.
In another issue, an authenticated remote attacker could add or modify internal object properties, resulting in undefined behavior.
CVE-2019-10768 and CVE-2019-11358 are the case numbers assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
In addition, an authenticated remote attacker could use specially crafted URLs to send a victim using PI Vision mobile to a vulnerable webpage due to a known issue in a third-party component.
CVE-2020-10600 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.5.
Also, an authenticated remote attacker with write access to PI Vision databases could inject code into a display. Unauthorized information disclosure, deletion, or modification is possible if a victim views the infected display.
CVE-2020-10614 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.4.
In another issue, a local attacker could view sensitive information in log files when service accounts are customized during installation or upgrade of PI Vision. The update fixes a previously reported issue.
CVE-2019-18244 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.1.
The product sees use in multiple sectors throughout the industry. It also sees action on a global basis.
No known public exploits specifically target these vulnerabilities. However, an attacker with low skill level could leverage the vulnerabilities.
OSIsoft reports the following workarounds and defensive measures:
CVE-2020-10610 — Manage permissions on HKLM\Software\PISystem and HKLM\WOW6432Node\Software\PISystem registry keys to block a high impact exploit path. See OSIsoft customer portal knowledge article PI System Registry Security Recommendations for details on setting registry permissions.
CVE-2019-18244 — Provision and use domain Group Managed Service Accounts or use the default NetworkService account to run PI Vision AppPools. There is no exposure to this vulnerability when using either of these account types. To limit exposure in case standard domain account is used to run PI Vision AppPools, remove the password entry from the setup log files immediately.
OSIsoft reports the following measures can be used to lower likelihood of exploitation:
CVE-2020-10610, CVE-2020-10608, CVE-2020-10606 — Migrate standard users to PI Vision and browser-based access to PI System data.
CVE-2020-10608 — Restrict network connections from PI client workstations to trusted AF servers (TCP Port 5457).
CVE-2020-10606 — Disable unused PI Buffering services from PI client workstations (PI Buffer Subsystem, PI Buffer Server).
CVE-2019-10768, CVE-2020-10600, CVE-2020-10614 — Limit write access to PI Vision displays to trusted users.
The following measures can be used to lower the potential impact of exploitation:
CVE-2020-10610 and CVE-2020-10608 — Deploy application whitelisting solutions with enforcement for approved DLLs:
- Windows AppLocker
- Windows Defender Application Control
- CVE-2020-10610 and CVE-2020-10608 — Monitor HKLM\Software\PISystem and HKLM\WOW6432Node\Software\PISystem registry keys as well as ProgramData\PISystem folder for unauthorized changes
- See OSIsoft customer portal knowledge article Monitoring PISystem Registry
For a list of PI System firewall port requirements, see knowledge base article KB01162 – Firewall Port Requirements.
CVE-2020-10604, CVE-2020-10602, CVE-2020-10600 — Fully configure Windows authentication for the PI System and disable legacy authentication methods. For a starting point on PI System security best practices, see knowledge base article KB00833 – Seven best practices for securing your PI Server.
For more information and workaround details for these vulnerabilities, click on OSIsoft’s Security Bulletin (registration required): OSIsoft Updates PI System and Common Components.

