OSIsoft LLC has an upgrade available to mitigate inclusion of sensitive information in log files and protection mechanism failure vulnerabilities in its PI Web API, according to a report from CISA.
Successful exploitation of these remotely exploitable vulnerabilities, which OSIsoft self-reported, may allow direct attacks against the product and disclose sensitive information. A RESTful service access layer, PI Web API 2018 and prior suffer from the issues.
In one hole, successful exploitation of this vulnerability may allow disclosure of sensitive information.
CVE-2019-13515 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 8.5.
In the other issue, the affected product is vulnerable to a direct attack due to a cross-site request forgery protection setting that has not taken effect.
CVE-2019-13516 has been assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
The product sees use in the chemical, critical manufacturing, energy, food and agriculture, government facilities, healthcare and public health, information technology, metals and mining, and water and wastewater systems sectors. It also sees action on a global basis.
No known public exploits specifically target these vulnerabilities. High skill level is needed to exploit.
OSIsoft recommends users upgrade to PI Web API 2018 SP1 or later to resolve these issues. To download PI Web API 2018 SP1, please access the OSIsoft customer portal (login required).
To avoid exposing sensitive information in the PI Web API Application Debug log, ensure the Debug log is disabled on the Windows machine running PI Web API.
Follow these steps to disable the Debug log:
1. Open Command Prompt and run the command eventvwr.msc
2. Navigate to View > Show Analytic and Debug Logs
3. Under Applications and Services Logs, find the PIWebAPI folder
4. Right click on the log entitled Debug, and click Disable Log
Also be sure to clear existing entries in the Debug log.
Assuming the log is Disabled but contains Events (e.g., after a troubleshooting session), enable the log and then disable it immediately.
If the log is already enabled, disable it, enable it, and finally disable it again to wipe out the contents.
The CSRF defense is enabled by default in new installations of PI Web API. OSIsoft recommends leaving the EnableCSRFDefense configuration setting unchanged so the CSRF defense is always in effect. If it is necessary to toggle this setting, OSIsoft recommends restarting the PI Web API service after changing the state.
For more information on these vulnerabilities, refer to OSIsoft’s Security Bulletin.
PI Web API Multiple security vulnerabilities resolved