# CVE-2012-4694: Weak cryptography in n/a

> Insufficient entropy in SSH and SSL keys allows man-in-the-middle attackers to spoof devices or modify data streams on Moxa industrial routers.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xw3x-gmvv-p64m

## What is CVE-2012-4694?

CVE-2012-4694 is a high-severity vulnerability in n/a, published on 15 Feb 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Moxa EDR-G903 series routers with firmware before 2.11 do not use a sufficient source of entropy for (1) SSH and (2) SSL keys, which makes it easier for man-in-the-middle attackers to spoof a device or modify a client-server data stream by leveraging knowledge of a key from a product installation elsewhere.

Weakness: CWE-310

## Which versions are affected by CVE-2012-4694?

It affects 2 products.


Products: Moxa Edr-G903, Moxa Edr G903 Firmware.

## How do I fix CVE-2012-4694?

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

## Is CVE-2012-4694 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4694 and fix it if it is affected.

What it is: CVE-2012-4694 is a high-severity vulnerability in n/a, published on 15 Feb 2013. 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-2012-4694 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-2012-4694/ (Markdown: https://insights.sbomify.com/CVE-2012-4694/index.md)
```

## Sources

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

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