# CVE-2014-5429: Denial of service in n/a

> Remote attackers can cause denial of service via malformed packets in Elipse SCADA and related products, affecting industrial control systems.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cqq2-prhp-3p28

## What is CVE-2014-5429?

CVE-2014-5429 is a medium-severity denial of service vulnerability in n/a, published on 6 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DNP Master Driver 3.02 and earlier in Elipse SCADA 2.29 build 141 and earlier, E3 1.0 through 4.6, and Elipse Power 1.0 through 4.6 allows remote attackers to cause a denial of service (CPU consumption) via malformed packets.

Weakness: CWE-399

## Which versions are affected by CVE-2014-5429?

It affects 3 products.


Products: Elipse E3, Elipse Power, Elipse Scada.

## How do I fix CVE-2014-5429?

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

## Is CVE-2014-5429 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0978](https://insights.sbomify.com/CVE-2015-0978/): Privilege escalation in n/a (medium 6.9)
- [CVE-2014-8652](https://insights.sbomify.com/CVE-2014-8652/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5429 and fix it if it is affected.

What it is: CVE-2014-5429 is a medium-severity denial of service vulnerability in n/a, published on 6 Dec 2014. 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-2014-5429 in the wild and no public exploit code.

Affected product: n/a. 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-2014-5429/ (Markdown: https://insights.sbomify.com/CVE-2014-5429/index.md)
```

## Sources

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

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