CVE-2016-0876
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 Secure Router EDR-G903 devices before 3.4.12 allow remote attackers to discover cleartext passwords by reading a configuration file.
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 Secure Router EDR-G903 devices before version 3.4.12 store passwords in cleartext within the device configuration file. Remote attackers can access this configuration file without proper authentication, allowing them to read and obtain plaintext passwords for the device.
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< 3.4.12CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Moxa EDR-G903 device is in your environmentIdentify all network devices and verify if any are Moxa EDR-G903 Secure Routers. Check device labels, management interface, or network inventory for the model number.Affected if You have a Moxa EDR-G903 device deployed in your network.
-
Determine the installed firmware versionAccess the device web interface or CLI and navigate to the firmware or system information page. Alternatively, use the command 'show version' via console or SSH to retrieve the firmware build number.Affected if The displayed firmware version is anything less than 3.4.12 (for example, 3.4.10, 3.3.x, or earlier).
-
Locate the device configuration fileAccess the device management interface and look for a backup, export, or configuration download feature. The configuration file is typically named something like config.bin, config.xml, or backup.cfg.Affected if You are able to download or access the device configuration file without authentication or with low-privilege credentials.
-
Inspect configuration for cleartext passwordsOpen the downloaded configuration file using a text editor or file viewer. Search for password fields, admin accounts, or credential entries. Check if any passwords appear as readable plaintext rather than hashed or encrypted strings.Affected if The configuration file contains plaintext passwords (for example, entries showing 'password=admin123' or similar readable credentials rather than hashes).
You are affected if you have an EDR-G903 device running firmware version lower than 3.4.12 that stores passwords in cleartext within an accessible configuration file.
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 data3.4.12
Upgrade the EDR-G903 firmware to version 3.4.12 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the device management interfaces using firewall rules or VLAN segmentation.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0876 — 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-2016-0876 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