dbcve.org
Edr G903 FirmwareApplication · Moxa

CVE-2012-4694

HIGH · 7.6 CVSS v2.0 Published 2013-02-15
Fix available
A fix is available. Upgrade to after 2.2 or later.
See remediation →
85/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The Moxa EDR-G903 routers with firmware before 2.11 use a weak or insufficient entropy source when generating SSH and SSL cryptographic keys, making keys predictable or reusable across devices. Attackers with knowledge of keys from one installation can perform man-in-the-middle attacks to spoof devices or modify traffic.

MitigationUpdate Moxa EDR-G903 firmware to version 2.11 or later to ensure proper entropy is used for key generation. After updating, regenerate SSH host keys and SSL certificates if reuse is suspected.

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
Edr G903 FirmwareApplication
Affected:<= 2.2= 1.0= 2.0= 2.1
Edr G903Hardware / appliance
Affected:all versions

CVSS 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
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/Au:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed firmware version
    Access the router's web interface or CLI and navigate to the firmware/version information section. Common paths: System > Firmware Update or Status > Device Information. Record the exact firmware version number.
    Affected if The firmware version is 1.0, 2.0, 2.1, 2.2, or any version lower than 2.11.
  2. Confirm SSH service status
    Check if the SSH service is enabled on the router. This is typically found under Network Services > SSH or Security > Access Control in the web interface. Note whether SSH access is configured.
    Affected if SSH is enabled and the firmware version is in the affected range (< 2.11).
  3. Inspect SSH host keys if accessible
    If you have CLI or filesystem access, navigate to the SSH configuration directory (commonly /etc/ssh or similar) and retrieve the SSH host keys (ssh_host_rsa_key, ssh_host_dsa_key). Check key creation timestamps or examine if multiple devices share identical keys.
    Affected if SSH host keys exist and were generated on a firmware version < 2.11, indicating predictable keys due to weak entropy.
  4. Confirm SSL/TLS service status
    Check if HTTPS or SSL-based management is enabled on the router. Look under Network Services > HTTPS or Security > Certificates in the web interface.
    Affected if HTTPS/SSL is enabled and the firmware version is in the affected range (< 2.11).
  5. Inspect SSL certificates if accessible
    If certificate storage is accessible via CLI or backup files, retrieve the SSL certificates. Compare certificate details (serial number, public key) against certificates from other EDR-G903 devices to detect reuse.
    Affected if SSL certificates were generated on a firmware version < 2.11, indicating potentially reusable or predictable certificates.

The device is affected if the installed firmware version is 2.2, 2.1, 2.0, 1.0, or any version prior to 2.11, and SSH or SSL services are enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.2
Interim mitigation

Update Moxa EDR-G903 firmware to version 2.11 or later to ensure proper entropy is used for key generation. After updating, regenerate SSH host keys and SSL certificates if reuse is suspected.

Fix this in Edr G903 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-4694 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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