CVE-2020-25167
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 · uneditedOSIsoft PI Vision 2020 versions prior to 3.5.0 could disclose information to a user with insufficient privileges for an AF attribute.
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 confidenceOSIsoft PI Vision 2020 versions prior to 3.5.0 contain an information disclosure vulnerability where users with insufficient privileges can view details about AF (Asset Framework) attributes they should not have access to, allowing unauthorized data exposure.
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< 3.5.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 PI Vision installation and versionCheck the installed PI Vision version in Windows Programs and Features, or query the PI Vision server for the assembly version (typically found in C:\Program Files\OSIsoft\PI Vision\ or via PI Vision diagnostic pages)Affected if The installed version is earlier than 3.5.0
-
Confirm AF (Asset Framework) is in useVerify whether the PI Vision environment is connected to PI Data Archive with AF elements or uses AF-based displays, by checking PI Vision connection settings or reviewing existing displays for AF data sourcesAffected if PI Vision is connected to an AF database and displays AF attributes to users
-
Review AF element security configurationExamine the AF hierarchy and element security settings in PI System Explorer to identify attributes with restricted or non-inherited access permissionsAffected if AF elements exist with attribute-level security that restricts user access
-
Audit PI Vision user roles and permissionsReview the PI Vision user roles in the PI Vision administration interface and check which roles have access to AF displays and attribute viewing capabilitiesAffected if Users with limited privileges are assigned to roles that can access PI Vision but should not see certain AF attribute details
You are affected if PI Vision version is earlier than 3.5.0, your environment uses AF functionality, and users with restricted permissions could potentially view AF attributes they should not access.
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.
dbcve · scoped3.5.0
Upgrade PI Vision to version 3.5.0 or later to remediate the privilege bypass vulnerability.
Pi Vision 3.5.0
- Identify current Pi Vision version by accessing the Pi Vision administration page or checking the installed software
- Plan and schedule the upgrade to Pi Vision 3.5.0 or later during a maintenance window
- Back up the existing Pi Vision configuration and database according to vendor documentation
- Download Pi Vision 3.5.0 or later from the AVEVA (formerly OSIsoft) customer portal
- Execute the installer following the official upgrade documentation from AVEVA
- Verify the upgrade completed successfully by checking the Pi Vision version
- Confirm that the authorization controls now properly restrict access to AF attributes based on user permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25167 — 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-25167 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