# CVE-2016-8353: Missing authorization in OSIsoft PI Web API 2015 R2 1.5.1

> Attackers can access the PI system without proper permissions due to a weakness in the OSIsoft PI Web API.

- **Severity:** Medium 6.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fj9p-xf89-pw63

## What is CVE-2016-8353?

CVE-2016-8353 is a medium-severity missing authorization vulnerability in OSIsoft PI Web API 2015 R2 1.5.1, published on 13 Feb 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in OSIsoft PI Web API 2015 R2 (Version 1.5.1). There is a weakness in this product that may allow an attacker to access the PI system without the proper permissions.

Weakness: CWE-264

## Which versions are affected by CVE-2016-8353?

It affects 1 product.


Products: Osisoft Pi Web Api 2015 R2.

## How do I fix CVE-2016-8353?

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

## Is CVE-2016-8353 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8353 and fix it if it is affected.

What it is: CVE-2016-8353 is a medium-severity missing authorization vulnerability in OSIsoft PI Web API 2015 R2 1.5.1, published on 13 Feb 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-8353 in the wild and no public exploit code.

Affected product: OSIsoft PI Web API 2015 R2 1.5.1. 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-2016-8353/ (Markdown: https://insights.sbomify.com/CVE-2016-8353/index.md)
```

## Sources

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

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