dbcve.org
Pi Data ArchiveApplication · Osisoft

CVE-2018-7529

HIGH · 7.5 CVSS v3.0 Published 2018-03-14
Fix available
A fix is available. Upgrade to after 2017 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A Deserialization of Untrusted Data issue was discovered in OSIsoft PI Data Archive versions 2017 and prior. Unauthenticated users may modify deserialized data to send custom requests that crash the server.

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 confidence

This is an insecure deserialization vulnerability in OSIsoft PI Data Archive versions 2017 and prior. Unauthenticated attackers can manipulate deserialized data to send custom requests that crash the server, resulting in denial of service.

MitigationUpgrade PI Data Archive to a version beyond 2017 that contains the security patch, or apply vendor-supplied patches if available. Network segmentation may also help limit 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
Pi Data ArchiveApplication
Affected:<= 2017

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 Data Archive version
    Use the PI System Management Tools (PI SMT) or check the Windows registry under HKLM\Software\OSIsoft\PI for the version entry, or run 'piartool -version' if available on the server
    Affected if The version is 2017 or any version prior to 2017 (e.g., 2016, 2015, etc.)
  2. Confirm PI Data Archive service is running
    Open Windows Services console (services.msc) and locate the 'PI Data Archive' or 'PI Server' service, or run 'sc query PI Data Archive' from command prompt
    Affected if The service is running - only an active service can be exploited for denial of service
  3. Check network listener status
    Use PI System Management Tools to view PI Data Archive network configuration, or check the piwebapi or PI SDK network binding settings
    Affected if The service is bound to a network interface and accepting remote connections - exploitation requires network accessibility to the affected port

A user is affected if their PI Data Archive installation is version 2017 or earlier AND the service is running and network-accessible, allowing unauthenticated attackers to trigger the deserialization flaw.

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 a release after 2017
Interim mitigation

Upgrade PI Data Archive to a version beyond 2017 that contains the security patch, or apply vendor-supplied patches if available. Network segmentation may also help limit exposure.

Fix this in Pi Data Archive Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7529 — 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-2018-7529 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