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

> Weak entropy in SSH and SSL keys allows remote attackers to predict keys and gain unauthorized access to Moxa OnCell Gateways.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/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:** 9 Aug 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rf95-4x65-x5hr

## What is CVE-2012-3039?

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

### Official description

Moxa OnCell Gateway G3111, G3151, G3211, and G3251 devices with firmware before 1.4 do not use a sufficient source of entropy for SSH and SSL keys, which makes it easier for remote attackers to obtain access by leveraging knowledge of a key from a product installation elsewhere.

Weakness: CWE-310

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

It affects 5 products.


Products: Moxa Oncell Gateway Firmware, Moxa Oncell Gateway G3111, Moxa Oncell Gateway G3151, Moxa Oncell Gateway G3211, Moxa Oncell Gateway G3251.

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

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

## Is CVE-2012-3039 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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