# CVE-2015-1013: SQL injection in n/a

> Authenticated users can bypass command restrictions and execute arbitrary SQL statements due to improper group configuration in OSIsoft PI SQL for AF.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 26 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gmcm-3fxg-fpm2

## What is CVE-2015-1013?

CVE-2015-1013 is a medium-severity SQL injection vulnerability in n/a, published on 26 May 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OSIsoft PI AF 2.6 and 2.7 and PI SQL for AF 2.1.2.19 do not ensure that the PI SQL (AF) Trusted Users group lacks the Everyone account, which allows remote authenticated users to bypass intended command restrictions via SQL statements.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2015-1013?

It affects 2 products.


Products: Osisoft Pi Server, Osisoft Pi Sql for Af.

## How do I fix CVE-2015-1013?

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

## Is CVE-2015-1013 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0209](https://insights.sbomify.com/CVE-2009-0209/): Weak cryptography in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1013 and fix it if it is affected.

What it is: CVE-2015-1013 is a medium-severity SQL injection vulnerability in n/a, published on 26 May 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1013 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-2015-1013/ (Markdown: https://insights.sbomify.com/CVE-2015-1013/index.md)
```

## Sources

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

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