CVE-2020-10606
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn OSIsoft PI System multiple products and versions, 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a local permission vulnerability in OSIsoft PI System where incorrect file system permissions allow a local attacker to access, modify, or delete data belonging to other users on the same machine. The vulnerability specifically impacts shared workstation or terminal server deployments where multiple users process PI System data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.6.8.26<= 2.0.2.5<= 4.8.0.18<= 1.0.0.54<= 1.1.0.10<= 1.2.0.6<= 1.2.0.42<= 1.2.1.71<= 1.2.2.79<= 1.3.0.1<= 1.3.0.130<= 1.3.1.135<= 1.4.0.17<= 1.5.0.88<= 2.5.19.0<= 3.4.430.460<= 2.5.19.0<= 2.2.0.183<= 1.5.0.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OSIsoft PI System componentsCheck Program Files for OSIsoft PI System directories, or review installed programs list. Look for PI API, PI Buffer Subsystem, PI Connector, PI Data Archive, PI Data Collection Manager, PI Integrator, or PI Interface Configuration Utility.Affected if Any of the affected products listed in the CVE are installed on the system.
-
Determine if system is a shared workstation or terminal serverCheck if the Windows OS is configured as a Remote Desktop Services terminal server, or if multiple user accounts actively use the same machine for PI System data processing.Affected if The system hosts multiple users who process PI System data on the same machine.
-
Locate PI System data directoriesIdentify the PI System installation directories (commonly under C:\Program Files\OSIsoft\ or C:\ProgramData\OSIsoft\) and locate the data folders where user-specific data is stored.Affected if PI System data directories exist on the machine.
-
Inspect file system permissions on PI data foldersRight-click the PI System data directories, select Properties, then Security tab. Review the permissions for users other than administrators and the system account. Check if non-privileged users have read, write, or modify access to directories belonging to other users.Affected if Users other than the data owner or administrator have permissions to read, modify, or delete data belonging to other users in the PI System directories.
-
Verify ACL configuration on shared PI foldersUse icacls command (e.g., icacls "C:\ProgramData\OSIsoft\PI" or relevant PI data path) to list explicit ACL entries. Examine whether access control lists properly restrict users to their own data folders.Affected if ACLs allow unauthorized users to access, modify, or delete files in other users' PI System data directories.
You are affected if any OSIsoft PI System component from the affected version list is installed on a shared workstation or terminal server where file system permissions improperly grant users access to other users' data directories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataCorrect file system permissions on PI System installations, particularly in shared/multi-user environments; restrict unauthorized users from accessing data directories and ensure proper access control lists are configured.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data