# CVE-2017-9655: Cross-site scripting in n/a

> An attacker can inject malicious scripts to redirect users to malicious sites in OSIsoft PI Integrator products.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v825-m7vv-ghg2

## What is CVE-2017-9655?

CVE-2017-9655 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Aug 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2017-9655?

It affects 3 products.


Products: Osisoft Pi Integrator for Business Analystics, Osisoft Pi Integrator for Microsoft Azure, Osisoft Pi Integrator for Sap Hana.

## How do I fix CVE-2017-9655?

No fix has been published for CVE-2017-9655 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9655 being exploited?

There is no known exploitation of CVE-2017-9655 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-9653](https://insights.sbomify.com/CVE-2017-9653/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9655 and fix it if it is affected.

What it is: CVE-2017-9655 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Aug 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9655 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9655/ (Markdown: https://insights.sbomify.com/CVE-2017-9655/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9655
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9655
- OSV: https://osv.dev/vulnerability/CVE-2017-9655

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9655/
Summaries are generated and may contain mistakes; the official description above is the record.