dbcve.org
Pi Af ClientApplication · Osisoft

CVE-2016-8365

MEDIUM · 5.5 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 1.4.6 / 2.8.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
OSIsoft PI System software (Applications using PI Asset Framework (AF) Client versions prior to PI AF Client 2016, Version 2.8.0; Applications using PI Software Development Kit (SDK) versions prior to PI SDK 2016, Version 1.4.6; PI Buffer Subsystem, versions prior to and including, Version 4.4; and PI Data Archive versions prior to PI Data Archive 2015, Version 3.4.395.64) operates between endpoints without a complete model of endpoint features potentially causing the product to perform actions based on this incomplete model, which could result in a denial of service. OSIsoft reports that in order to exploit the vulnerability an attacker would need to be locally connected to a server. A CVSS v3 base score of 7.1 has been calculated; the CVSS vector string is (AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H)

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 confidence

The PI System software components (AF Client, PI SDK, PI Buffer Subsystem, PI Data Archive) operate between endpoints without properly modeling endpoint capabilities. This incomplete model of endpoint features can cause the product to perform incorrect actions leading to a denial of service condition. The vulnerability requires local access to the server for exploitation.

MitigationUpdate affected components to the specified versions: PI AF Client 2016 v2.8.0 or later, PI SDK 2016 v1.4.6 or later, PI Buffer Subsystem v4.4.1 or later, and PI Data Archive 2015 v3.4.395.64 or later. Since the attack requires local access, ensure servers are in secured physical locations with restricted access.

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
Pi Af ClientApplication
Affected:< 2.8.0
Pi Buffer SubsystemApplication
Affected:< 4.5.0
Pi Data ArchiveApplication
Affected:< 3.4.400.1162
Pi SdkApplication
Affected:< 1.4.6

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PI System components
    Enumerate the OSIsoft PI System components present on the machine. Common locations include C:\Program Files\OSIsoft\ or C:\Program Files (x86)\OSIsoft\. Look for subdirectories corresponding to AF Client, PI SDK, PI Buffer Subsystem, and PI Data Archive.
    Affected if Any of the four affected components (AF Client, PI SDK, PI Buffer Subsystem, PI Data Archive) are found on the system
  2. Check PI AF Client version
    Locate the PI AF Client installation and retrieve its version information, typically found in the assembly metadata, product information file, or via the program properties in Add/Remove Programs.
    Affected if The installed version is earlier than 2.8.0
  3. Check PI SDK version
    Locate the PI SDK installation and retrieve its version information, typically found in the assembly metadata, product information file, or via the program properties in Add/Remove Programs.
    Affected if The installed version is earlier than 1.4.6
  4. Check PI Buffer Subsystem version
    Locate the PI Buffer Subsystem installation and retrieve its version information, typically found in the assembly metadata, product information file, or via the program properties in Add/Remove Programs.
    Affected if The installed version is earlier than 4.5.0
  5. Check PI Data Archive version
    Locate the PI Data Archive installation and retrieve its version information, typically found in the assembly metadata, product information file, or via the program properties in Add/Remove Programs.
    Affected if The installed version is earlier than 3.4.400.1162

The environment is affected if any of the four PI System components (AF Client, PI SDK, PI Buffer Subsystem, or PI Data Archive) are installed at a version below the thresholds (2.8.0, 1.4.6, 4.5.0, and 3.4.400.1162 respectively).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.4.6 / 2.8.0 / 3.4.400.1162 or later
Fixed in 1.4.62.8.03.4.400.1162
Interim mitigation

Update affected components to the specified versions: PI AF Client 2016 v2.8.0 or later, PI SDK 2016 v1.4.6 or later, PI Buffer Subsystem v4.4.1 or later, and PI Data Archive 2015 v3.4.395.64 or later. Since the attack requires local access, ensure servers are in secured physical locations with restricted access.

Fix this in Pi Af Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8365 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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