# CVE-2014-5409: GE Hydran M2 Predictable Value Range from Previous Values

> Remote attackers can spoof packets on GE Hydran M2 devices by predicting weak TCP Initial Sequence Numbers generated by the Ethernet card.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 14 Mar 2015
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-w7hr-2cw5-qqgq

## What is CVE-2014-5409?

CVE-2014-5409 is a medium-severity vulnerability in GE Hydran M2, containing the 17046 Ethernet option, published on 14 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 17046 Ethernet card before 94450214LFMT100SEM-L.R3-CL for the GE Digital Energy Hydran M2 does not properly generate random values for TCP Initial Sequence Numbers (ISNs), which makes it easier for remote attackers to spoof packets by predicting these values.

Weakness: CWE-343 (Predictable Value Range from Previous Values)

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

It affects 1 product.


Products: Ge Hydran M2.

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

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

## Is CVE-2014-5409 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5409 is a medium-severity vulnerability in GE Hydran M2, containing the 17046 Ethernet option, published on 14 Mar 2015. 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-5409 in the wild and no public exploit code.

Affected product: GE Hydran M2, containing the 17046 Ethernet option. 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-5409/ (Markdown: https://insights.sbomify.com/CVE-2014-5409/index.md)
```

## Sources

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

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