Pi Integrator For Business AnalysticsApplication · Osisoft

CVE-2017-9655

MEDIUM · 5.4 CVSS v3.0 Published 2017-08-14
Fix available
A fix is available. Upgrade to after 2016 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Cross-Site Scripting issue was discovered in OSIsoft PI Integrator for Business Analytics before 2016 R2, PI Integrator for Microsoft Azure before 2016 R2 SP1, and PI Integrator for SAP HANA before 2017. An attacker may be able to upload a malicious script that attempts to redirect users to a malicious web site.

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

Stored Cross-Site Scripting (XSS) vulnerability in OSIsoft PI Integrator products (Business Analytics <2016 R2, Microsoft Azure <2016 R2 SP1, SAP HANA <2017) allows attackers to upload malicious scripts via the integrator's upload functionality, potentially redirecting users to malicious websites.

MitigationUpgrade affected PI Integrator products to the specified versions (2016 R2 or later for Business Analytics, 2016 R2 SP1 or later for Azure, 2017 or later for SAP HANA). Additionally, implement input validation on upload functions and output encoding for user-supplied content.

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 Integrator For Business AnalysticsApplication
Affected:<= 2016
Pi Integrator For Microsoft AzureApplication
Affected:<= 2016
Pi Integrator For Sap HanaApplication
Affected:<= 2016

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify installed PI Integrator product
    Locate the OSIsoft PI Integrator installation on the system. Check Programs and Features (Windows) or use system inventory tools to list installed OSIsoft products. Identify which integrator is present: Business Analytics, Microsoft Azure, or SAP HANA.
    Affected if Any of the three PI Integrator products (Business Analytics, Azure, or SAP HANA) is installed and the version is 2016 or earlier.
  2. Determine installed product version
    Open the Windows Control Panel, go to Programs and Features, find the OSIsoft PI Integrator entry, and note the version number. Alternatively, check the installation directory for version information or run the integrator'sAbout or diagnostics command if available.
    Affected if The installed version is 2016 or any version <= 2016 for any of the three integrator products.
  3. Verify upload functionality status
    Access the PI Integrator web interface or administrative console. Navigate to the upload or data import settings. Check whether the upload functionality is enabled and accessible to users.
    Affected if The upload feature is enabled and accessible, providing an attack vector for the stored XSS.
  4. Review upload configuration settings
    Examine the integrator's configuration files or web.config for upload-related settings. Look for parameters controlling file upload size, allowed file types, and input validation settings.
    Affected if Upload functionality is present with no or minimal input validation configured.

A system is affected if any OSIsoft PI Integrator product (Business Analytics, Azure, or SAP HANA) version 2016 or earlier is installed with the upload functionality enabled and accessible.

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 2016
Interim mitigation

Upgrade affected PI Integrator products to the specified versions (2016 R2 or later for Business Analytics, 2016 R2 SP1 or later for Azure, 2017 or later for SAP HANA). Additionally, implement input validation on upload functions and output encoding for user-supplied content.

Fix this in Pi Integrator For Business Analystics Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9655 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9655 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