CVE-2019-18275
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, All versions of PI Vision prior to 2019. The affected product is vulnerable to an improper access control, which may return unauthorized tag data when viewing analysis data reference attributes.
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 · high confidencePI Vision versions prior to 2019 contain an improper access control vulnerability that allows unauthorized retrieval of tag data through analysis data reference attributes. This authorization bypass in the web-based visualization tool permits users to access data they should not have permissions to view.
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< 2019CVSS 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 versionLocate the PI Vision installation directory and check the version information, typically found in assembly files, installer logs, or the PI Vision system information page accessible through the administration interfaceAffected if The installed version is any release prior to the 2019 release (versions numbered below 2019)
-
Verify Analysis data reference usageInspect the PI Vision displays and analyses configured in the system to determine if any utilize data reference attributes, which are the specific feature through which the unauthorized data retrieval can occurAffected if Analysis data reference attributes are configured and accessible to users who should not have permission to view certain tag data
-
Review user access control policiesExamine the PI Vision user and group permissions configuration to identify what tag data each user or group is authorized to access versus what they can actually retrieve through analysis data reference attributesAffected if Users without full permissions to specific tags can retrieve tag data through analysis data reference attributes that should be restricted
-
Test unauthorized tag data accessUsing a user account with limited permissions, attempt to access tag data via analysis data reference attributes on displays or analyses that the user should not have permission to viewAffected if The restricted user can successfully retrieve tag data they were not explicitly granted permission to access
The environment is affected if PI Vision version is prior to 2019 AND analysis data reference attributes are in use, allowing users to bypass intended access controls and retrieve tag data outside their authorized permissions.
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 data2019
Upgrade PI Vision to version 2019 or later to obtain the patched release that addresses the improper access control. Verify access control policies post-upgrade.
- 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-2019-18275 — 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-2019-18275 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