# CVE-2018-11052: Dell EMC ECS S3 Authentication Bypass Vulnerability

> Remote attackers can bypass authentication to read and modify S3 objects in Dell EMC ECS, requiring immediate patching.

- **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:** 3 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g9jf-xxjf-qx55

## What is CVE-2018-11052?

CVE-2018-11052 is a critical authentication bypass vulnerability in Dell EMC ECS, published on 3 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dell EMC ECS versions 3.2.0.0 and 3.2.0.1 contain an authentication bypass vulnerability. A remote unauthenticated attacker could exploit this vulnerability to read and modify S3 objects by supplying specially crafted S3 requests.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-11052?

It affects 1 product.


Products: Dellemc Elastic Cloud Storage.

## How do I fix CVE-2018-11052?

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

## Is CVE-2018-11052 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11052 and fix it if it is affected.

What it is: CVE-2018-11052 is a critical authentication bypass vulnerability in Dell EMC ECS, published on 3 Jul 2018. 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-2018-11052 in the wild and no public exploit code.

Affected product: Dell EMC ECS. 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-2018-11052/ (Markdown: https://insights.sbomify.com/CVE-2018-11052/index.md)
```

## Sources

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

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