CVE-2012-3039
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMoxa 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMoxa OnCell Gateway devices (G3111, G3151, G3211, G3251) with firmware before 1.4 use insufficient entropy sources when generating SSH and SSL cryptographic keys, causing keys to be predictable or reusable across different installations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.3all versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:S/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the OnCell Gateway modelAccess the device web interface or console and locate the model number (G3111, G3151, G3211, or G3251) in the device status or system information pageAffected if The model is G3111, G3151, G3211, or G3251 - these specific models are listed as affected in all versions
-
Check the installed firmware versionIn the device web interface, go to System > Firmware or System > Status to view the current firmware version. Alternatively, use the console command 'show version' or check the system information pageAffected if The firmware version is 1.3 or earlier, or the firmware version cannot be determined (unknown versions of these models are still potentially affected)
-
Verify if SSH service is enabledIn the device web interface, go to Network > SSH or Security > Services and check if SSH is turned on. From console, run 'show ssh status' or check the service configurationAffected if SSH is enabled - the vulnerability affects SSH key generation, so this service must be active for the flaw to be exploitable
-
Verify if SSL/TLS service is enabledIn the device web interface, go to Network > SSL, Security > Web Server, or Security > HTTPS and check if SSL/TLS is enabled for web access or other servicesAffected if SSL/TLS is enabled - the vulnerability affects SSL key generation, so this service must be active for the flaw to be exploitable
The device is affected if it is an OnCell Gateway G3111, G3151, G3211, or G3251 model with firmware 1.3 or earlier, or any firmware version of these specific models when SSH or SSL services are enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade firmware to version 1.4 or later and regenerate all SSH and SSL keys on affected devices.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3039 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3039 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data