CVE-2020-10608
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 plant a binary and bypass a code integrity check for loading PI System libraries. This exploitation can target another local user of PI System software on the computer to escalate privilege and result in unauthorized information disclosure, deletion, or modification.
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 privilege escalation vulnerability in OSIsoft PI System where an attacker can plant a malicious binary and bypass code integrity checks when loading PI System libraries. Successful exploitation allows targeting another local user to escalate privileges and achieve unauthorized data access, modification, or deletion.
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 productsCheck Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'OSIsoft' or 'PI' or check Program Files for OSIsoft PI folders. Alternatively, use 'Get-ItemProperty' PowerShell command on 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' to list installed programs and filter for OSIsoft products.Affected if Any OSIsoft PI product is installed on the system
-
Determine installed version of PI APICheck the DLL version of PI API library (piapi.dll) typically found in C:\Program Files\Common Files\OSIsoft\PI or check registry key HKLM\SOFTWARE\OSIsoft\PI for version information.Affected if Version is <= 1.6.8.26 or <= 2.0.2.5
-
Determine installed version of PI Data ArchiveCheck the PI Data Archive version via PI System Management Tools, or check the installed version through Windows Programs and Features, or query the PISDK version programmatically if available.Affected if Version is <= 3.4.430.460
-
Determine installed version of PI Connector or PI Connector RelayCheck Windows Programs and Features for the specific Connector version, or check the executable version of the Connector service typically installed in C:\Program Files\OSIsoft\PI Connector.Affected if Connector version is <= 1.5.0.88 or Connector Relay version is <= 2.5.19.0
-
Check for code integrity enforcement on PI library loadingReview Windows code integrity policies using 'gpedit.msc' under Computer Configuration > Windows Settings > Security Settings > Code Integrity, or check for AppLocker policy enforcement status via 'Get-AppLockerPolicy -Effective' in PowerShell.Affected if Code integrity or AppLocker policies are not enforced or are misconfigured to allow unsigned PI libraries
A system is affected if any OSIsoft PI product is installed with a version matching the affected ranges AND code integrity policies are not properly blocking unauthorized library loading.
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 dataApply available vendor patches for affected PI System products and versions; review and enforce code integrity policies to prevent unauthorized library loading.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10608 — 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-10608 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