# CVE-2015-7425: Privilege escalation in n/a

> Remote attackers can gain administrative privileges and execute back-end functions via a crafted URL in IBM Tivoli Storage Manager for VMware.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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:** 21 Feb 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-65jh-q77m-pwj8

## What is CVE-2015-7425?

CVE-2015-7425 is a critical vulnerability in n/a, published on 21 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Data Protection component in the VMware vSphere GUI in IBM Tivoli Storage Manager for Virtual Environments: Data Protection for VMware (aka Spectrum Protect for Virtual Environments) 6.3 before 6.3.2.5, 6.4 before 6.4.3.1, and 7.1 before 7.1.4 and Tivoli Storage FlashCopy Manager for VMware (aka Spectrum Protect Snapshot) 3.1 before 3.1.1.3, 3.2 before 3.2.0.6, and 4.1 before 4.1.4 allows remote attackers to obtain administrative privileges via a crafted URL that triggers back-end function execution.

Weakness: CWE-264

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

It affects 2 products.


Products: Ibm Tivoli Storage Flashcopy Manager for Vmware, Ibm Tivoli Storage Manager for Virtual Environments Data Protection for Vmware.

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

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

## Is CVE-2015-7425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6033](https://insights.sbomify.com/CVE-2016-6033/): Cross-site request forgery in Tivoli Storage Manager for Virtual Environments (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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