# CVE-2017-8021: EMC Elastic Cloud Storage (ECS) before 3.1 is affected by an undocumented account vulnerability that could potentially be leveraged by malic


- **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
- **Fix available:** No
- **Published:** 2 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rpgj-f22q-phgr

## What is CVE-2017-8021?

CVE-2017-8021 is a critical vulnerability in EMC Elastic Cloud Storage all versions prior to 3.1, published on 2 Oct 2017. 

### Official description

EMC Elastic Cloud Storage (ECS) before 3.1 is affected by an undocumented account vulnerability that could potentially be leveraged by malicious users to compromise the affected system.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Dell Elastic Cloud Storage.

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

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

## Is CVE-2017-8021 being exploited?

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

## Other vulnerabilities in EMC Elastic Cloud Storage all versions prior to 3.1

- [CVE-2026-40636](https://insights.sbomify.com/CVE-2026-40636/): Hardcoded credentials in ECS (critical 9.8)
- [CVE-2026-22273](https://insights.sbomify.com/CVE-2026-22273/): Hardcoded credentials in ObjectScale (high 8.8)
- [CVE-2025-26476](https://insights.sbomify.com/CVE-2025-26476/): Hardcoded credentials in ECS (high 8.4)
- [CVE-2024-51540](https://insights.sbomify.com/CVE-2024-51540/): Integer overflow in ECS (high 8.1)
- [CVE-2026-28261](https://insights.sbomify.com/CVE-2026-28261/): Information disclosure in Elastic Cloud Storage (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8021 is a critical vulnerability in EMC Elastic Cloud Storage all versions prior to 3.1, published on 2 Oct 2017. 
Exploitation: There is no known exploitation of CVE-2017-8021 in the wild and no public exploit code.

Affected product: EMC Elastic Cloud Storage all versions prior to 3.1. 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-8021/ (Markdown: https://insights.sbomify.com/CVE-2017-8021/index.md)
```

## Sources

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

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