# CVE-2015-2116: Other in n/a

> Remote authenticated users can execute arbitrary code or cause denial of service in HP Storage Data Protector.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **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 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6xr-w7q5-p5hr

## What is CVE-2015-2116?

CVE-2015-2116 is a critical vulnerability in n/a, published on 26 Apr 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in HP Storage Data Protector 7.x before 7.03 build 107 allows remote authenticated users to execute arbitrary code or cause a denial of service via unknown vectors.

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

It affects 1 product.


Products: Hp Storage Data Protector.

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

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

## Is CVE-2015-2116 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2623](https://insights.sbomify.com/CVE-2014-2623/): Other in n/a (critical 10.0)
- [CVE-2013-2344](https://insights.sbomify.com/CVE-2013-2344/): Other in n/a (critical 10.0)
- [CVE-2013-2345](https://insights.sbomify.com/CVE-2013-2345/): Other in n/a (critical 10.0)
- [CVE-2013-2346](https://insights.sbomify.com/CVE-2013-2346/): Other in n/a (critical 10.0)
- [CVE-2013-2347](https://insights.sbomify.com/CVE-2013-2347/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2116 is a critical vulnerability in n/a, published on 26 Apr 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-2116 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-2116/ (Markdown: https://insights.sbomify.com/CVE-2015-2116/index.md)
```

## Sources

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

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