# CVE-2017-1710: Privilege escalation in Storwize V7000 (2076)

> A remote attacker can escalate privileges via the Service Assistant GUI in IBM Storwize V7000 storage systems.

- **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:** 13 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j25f-cxxh-862j

## What is CVE-2017-1710?

CVE-2017-1710 is a critical vulnerability in IBM Storwize V7000 (2076), published on 13 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Service Assistant GUI in IBM Storwize V7000 (2076) 8.1 could allow a remote attacker to perform a privilege escalation. IBM X-Force ID: 134531.

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

It affects 4 products.


Products: Ibm Flashsystem V9000 Firmware, Ibm San Volume Controller Firmware, Ibm Storwize V5000 Firmware, Ibm Storwize V7000 Firmware.

## How do I fix CVE-2017-1710?

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

## Is CVE-2017-1710 being exploited?

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

## Other vulnerabilities in IBM Storwize V7000 (2076)

- [CVE-2015-7446](https://insights.sbomify.com/CVE-2015-7446/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1710 is a critical vulnerability in IBM Storwize V7000 (2076), published on 13 Nov 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-1710 in the wild and no public exploit code.

Affected product: IBM Storwize V7000 (2076). 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-1710/ (Markdown: https://insights.sbomify.com/CVE-2017-1710/index.md)
```

## Sources

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

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