OSIsoft Mitigates PI System Issue

Tuesday, November 8, 2016 @ 04:11 PM gHale


OSIsoft created new versions to mitigate an incomplete model of endpoint features vulnerability in its PI System software, according to a report with ICS-CERT.

Successful exploitation of this vulnerability could cause a shutdown of the PI Data Archive or connected applications. In the case of the PI Buffer Subsystem Service, this shutdown can result in unrecoverable data loss. Desktop clients, web servers, and other data access servers could also be potential targets of this type of shutdown.

RELATED STORIES
Siemens Privilege Escalation Hole
Phoenix Contact ILC Mitigation Plan
Moxa OnCell Security Vulnerabilities
Schneider Working to Mitigate HMI Holes

The following PI System software versions suffer from the issue:
• Applications using PI Asset Framework (AF) Client versions prior to PI AF Client 2016, Version 2.8.0
• Applications using PI Software Development Kit (SDK) versions prior to PI SDK 2016, Version 1.4.6
• PI Buffer Subsystem, versions prior to and including, Version 4.4
• PI Data Archive versions prior to PI Data Archive 2015, Version 3.4.395.64

OSIsoft is a U.S.-based company that maintains headquarters in San Leandro, California, with global operations.

The affected products are PI AF Client, PI SDK, PI Buffer Subsystem, and PI Data Archive. The AF Client is a repository for asset-centric models, hierarchies, objects, and equipment. The PI SDK is a programming library providing access to PI Servers. PI AF Client and PI SDK are frequently included with other software packages. The PI Data Archive is the core server technology used in the PI System for real time data storage and distribution of instrument data. PI Buffer Subsystem provides buffering for most current PI Client applications, as well as PI Interfaces. These products see action across multiple sectors. OSIsoft estimates these products see use on a global basis.

The affected products operate between endpoints without a complete model of endpoint features potentially causing the product to perform actions based on this incomplete model, which could result in a denial of service. OSIsoft reports in order to exploit the vulnerability an attacker would need to be locally connected to a server.

CVE-2016-8365 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.1.

This vulnerability is not exploitable remotely.

No known public exploits specifically target this vulnerability. However, an attacker with a low skill would be able to exploit this vulnerability.

To fully address potential for data loss or disconnection due to this issue, OSIsoft said should upgrade to:
• PI Buffer Subsystem, Version 4.5.0 or later
• PI AF Client 2016, Version 2.8.0 or later
• PI SDK 2016, Version 1.4.6 or later
• PI Data Archive 2016, Version 3.4.400.1162 or later

For additional information about the vulnerability and recommended mitigation plan, OSIsoft’s security bulletin AL00308, OSIsoft Releases Security Updates for Core Networking Component in PI System 2016.

In order to perform the upgrades, users can use the PI AF Client 2016 Install Kit to upgrade PI AF Client and the PI Buffer Subsystem together. Users can use the PI SDK 2016 Install Kit to upgrade the PI SDK. If PI Buffer Subsystem is installed on a machine without PI AF Client, users can use the PI Interface Configuration Utility (ICU) Install Kit (1.4.16.79B) to upgrade buffering without installing the PI AF Client software.

OSIsoft also offers the following defensive measures:
• Use transport security protection for all remote connections to the PI Data Archive Server to block attacks from adjacent networks.
• PI AF Client 2015, Version 2.7 and PI Buffer Subsystem, Version 4.4 automatically enable transport security with PI Data Archive Server 2015, Version 3.4.395.64 or later when the connecting application uses Windows Integrated Security (WIS).
• In order to verify an application is connecting with WIS and using transport security, review the PI Data Archive Server message log entries. For each successful connection, there will be a message with event ID 7082. The Method should be “Windows Login,” and if the connection is using transport security, then the ciphers will also be listed.
• If users are running PI Data Archive PR1, Version 3.4.375.38, to avoid data loss, it is imperative to upgrade PI SDK, PI AF Client, and PI Buffer Subsystem nodes before the PI Data Archive.



Leave a Reply

You must be logged in to post a comment.