# CVE-2017-8011: Hardcoded credentials in EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net)

> Remote attackers can use undocumented default credentials to execute arbitrary commands on EMC storage management systems.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 17 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8wj-7m8m-j6c8

## What is CVE-2017-8011?

CVE-2017-8011 is a critical vulnerability in EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net), published on 17 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R for SAS Solution Packs (EMC ViPR SRM prior to 4.1, EMC Storage M&R prior to 4.1, EMC VNX M&R all versions, EMC M&R (Watch4Net) for SAS Solution Packs all versions) contain undocumented accounts with default passwords for Webservice Gateway and RMI JMX components. A remote attacker with the knowledge of the default password may potentially use these accounts to run arbitrary web service and remote procedure calls on the affected system.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 4 products.


Products: Dell Emc M\&r, Dell Emc Storage Monitoring and Reporting, Dell Emc Vipr Srm, Dell Emc Vnx Monitoring and Reporting.

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

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

## Is CVE-2017-8011 being exploited?

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

## Other vulnerabilities in EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net)

- [CVE-2017-8007](https://insights.sbomify.com/CVE-2017-8007/): Path traversal in EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net) for SAS Solution Packs (high 8.8)
- [CVE-2017-8012](https://insights.sbomify.com/CVE-2017-8012/): Denial of service in EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net) for SAS Solution Packs (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8011 is a critical vulnerability in EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net), published on 17 Jul 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-8011 in the wild and no public exploit code.

Affected product: EMC ViPR SRM, EMC Storage M&R, EMC VNX M&R, EMC M&R (Watch4Net). 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-8011/ (Markdown: https://insights.sbomify.com/CVE-2017-8011/index.md)
```

## Sources

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

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