# CVE-2017-9653: Missing authorization in n/a

> An attacker can gain unauthorized privileged access to OSIsoft PI Integrator systems due to improper authorization checks.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4xvh-24fg-v9xx

## What is CVE-2017-9653?

CVE-2017-9653 is a critical missing authorization vulnerability in n/a, published on 14 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Authorization 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 is able to gain privileged access to the system while unauthorized.

Weakness: CWE-863 (Incorrect Authorization)

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

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-9653?

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

## Is CVE-2017-9653 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9655](https://insights.sbomify.com/CVE-2017-9655/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9653 is a critical missing authorization vulnerability in n/a, published on 14 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9653 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-9653/ (Markdown: https://insights.sbomify.com/CVE-2017-9653/index.md)
```

## Sources

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

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