The vulnerability, if exploited, could allow an unauthenticated miscreant to perform read operations intended only for PIMBoards users, resulting in information disclosure. Write operations are not impacted.
AVEVA recommends the following general defensive measures:
* Restrict Network Access: Implement host-based and/or network firewall controls on all nodes hosting the PIMBoards API to ensure that only trusted client systems are permitted to establish connections.
* Apply strong Access Control Lists to all folders storing project files to ensure only trusted users have read-access.
* Maintain a trusted chain-of-custody on project files during creation, modification, distribution, backups, and use.
AVEVA recommends that organizations evaluate the impact of these vulnerabilities based on their operational environment, architecture, and product implementation. Customers using affected product versions or affected PIMBoards project files should take the following actions to mitigate the risk of exploit:
* Apply AVEVA Pipeline Integrity Monitor 2025 SP1 P2 Security Update and migrate old project files.
* For project files that cannot be migrated (e.g. backups or transient copies), evaluate the risk of potential password leakage from these files and implement stricter read access controls to protect these unsafe files.
* Require AVEVA Pipeline Integrity Monitor PIMBoards users to change their passwords.
Important: PIMBoards Project Files migration from older versions to AVEVA Pipeline Integrity Monitor 2025 SP1 P2 is one-way due to the changes in password hashing algorithms and end-user managed encryption keys.