# CVE-2018-8847: Memory corruption in Eaton 9000X Drive

> A stack-based buffer overflow in Eaton 9000X DriveA allows remote attackers to execute arbitrary code on the device.

- **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:** 13 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v547-ggh4-4xpf

## What is CVE-2018-8847?

CVE-2018-8847 is a critical memory corruption vulnerability in ICS-CERT Eaton 9000X Drive, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eaton 9000X DriveA versions 2.0.29 and prior has a stack-based buffer overflow vulnerability, which may allow remote code execution.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Eaton 9000x Firmware.

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

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

## Is CVE-2018-8847 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8847 is a critical memory corruption vulnerability in ICS-CERT Eaton 9000X Drive, published on 13 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-8847 in the wild and no public exploit code.

Affected product: ICS-CERT Eaton 9000X Drive. 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-8847/ (Markdown: https://insights.sbomify.com/CVE-2018-8847/index.md)
```

## Sources

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

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