# CVE-2025-0960: AutomationDirect C-more EA9 HMI Classic Buffer Overflow

> An attacker can exploit a buffer overflow in AutomationDirect C-more EA9 HMI devices to achieve remote code execution or cause denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-6p26-vpff-6gxm

## What is CVE-2025-0960?

CVE-2025-0960 is a critical memory corruption vulnerability in AutomationDirect C-more EA9 HMI EA9-RHMI, published on 4 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AutomationDirect C-more EA9 HMI contains a function with bounds checks that can be skipped, which could result in an attacker abusing the function to cause a denial-of-service condition or achieving remote code execution on the affected device.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-0960?


## How do I fix CVE-2025-0960?

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

## Is CVE-2025-0960 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0960 and fix it if it is affected.

What it is: CVE-2025-0960 is a critical memory corruption vulnerability in AutomationDirect C-more EA9 HMI EA9-RHMI, published on 4 Feb 2025. 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-2025-0960 in the wild and no public exploit code.

Affected product: AutomationDirect C-more EA9 HMI EA9-RHMI. 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-2025-0960/ (Markdown: https://insights.sbomify.com/CVE-2025-0960/index.md)
```

## Sources

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

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