# CVE-2017-9641: Cross-site request forgery in PI Coresight

> A cross-site request forgery flaw in PI Coresight allows attackers to access the PI system, requiring an upgrade to PI Vision for mitigation.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6jmm-p5w8-6rvr

## What is CVE-2017-9641?

CVE-2017-9641 is a high-severity vulnerability in OSIsoft PI Coresight, published on 25 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PI Coresight 2016 R2 contains a cross-site request forgery vulnerability that may allow access to the PI system. OSIsoft recommends that users upgrade to PI Vision 2017 or greater to mitigate this vulnerability.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Osisoft Pi Coresight.

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

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

## Is CVE-2017-9641 being exploited?

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

## Other vulnerabilities in OSIsoft PI Coresight

- [CVE-2017-5153](https://insights.sbomify.com/CVE-2017-5153/): Information disclosure in OSIsoft PI Coresight and PI Web API (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9641 is a high-severity vulnerability in OSIsoft PI Coresight, published on 25 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9641 in the wild and no public exploit code.

Affected product: OSIsoft PI Coresight. 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-9641/ (Markdown: https://insights.sbomify.com/CVE-2017-9641/index.md)
```

## Sources

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

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