Vulnerability Note VU#479051

OSIsoft PI Server provides an insecure authentication mechanism

Original Release date: 19 Nov 2010 | Last revised: 19 Nov 2010


OSIsoft PI Server provides an insecure authentication mechanism that could allow attackers to read or modify information in databases.


PI Server is a core component of the OSIsoft PI System.

According to a report from C4 Security, OSISoft release notes (login required) for PI Server 3.4.380.36, and OSISoft KB article 5120OSI8, it appears that changes were made to PI Server to better resist brute force authentication attempts. PI Server 3.4.380.36 deprecates an older authentication mechanism in favor of Microsoft Windows authentication.

Windows authentication provides security features such as: logging failed login attempts, enforcing minimum password lengths, and enforcing password time-outs.


According to reports it appears that the old PI Sever integrated authentication security system method was susceptible to brute force authentication attempts. A successful attempt will allow an attacker to gain access to the PI Server databases.


OSIsoft recommends upgrading to PI Server version 3.4.380.36.

According to the PI Server 3.4.380.36 release notes the following procedures to mitigate the vulnerability:

Enable the PI Server for Windows authentication and configure PI Trust records
Use IPSec between the PI Server and the different client computers

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
OSIsoftAffected12 Sep 200812 Nov 2010
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



Thanks to Eyal Udassin at C4 Security for reporting this vulnerability.

This document was written by Michael Orlando.

Other Information

  • CVE IDs: CVE-2009-0209
  • Date Public: 30 Sep 2009
  • Date First Published: 19 Nov 2010
  • Date Last Updated: 19 Nov 2010
  • Severity Metric: 11.76
  • Document Revision: 37


If you have feedback, comments, or additional information about this vulnerability, please send us email.