CVE-2016-9346
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 · uneditedAn issue was discovered in Moxa MiiNePort E1 versions prior to 1.8, E2 versions prior to 1.4, and E3 versions prior to 1.1. Configuration data are stored in a file that is not encrypted.
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 confidenceThe Moxa MiiNePort E1, E2, and E3 serial-to-ethernet device gateways store configuration data in plain text files without encryption. This allows attackers with file system access to read sensitive configuration information such as credentials and network settings.
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.7<= 1.3<= 1.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify device model and firmware versionAccess the device web interface, console, or management API and retrieve the model number (E1, E2, or E3) and current firmware version. This is typically found in the system status or firmware upgrade section of the web UI or via CLI command.Affected if Firmware version is E1 <= 1.7, E2 <= 1.3, or E3 <= 1.0
-
Locate configuration file storageAccess the device file system via FTP, SCP, SD card slot, or console if accessible. Navigate to the configuration directory where settings are stored - commonly /etc, /config, or a dedicated config folder on the device's file system.Affected if Configuration files exist and are accessible via file system access
-
Inspect configuration file contents for plain text credentialsOpen the primary configuration file (often named config.ini, config.xml, system.conf, or similar) and search for stored usernames and passwords in plain text format rather than encrypted or hashed values.Affected if Usernames, passwords, or network keys appear in plain text within configuration files
-
Verify encryption status of configuration dataExamine configuration files for indicators of encryption such as base64 encoding, encrypted blobs, or known encryption markers. Compare multiple configuration backups if available to see if sensitive fields are consistently readable.Affected if No encryption indicators found and sensitive fields are readable as plain text
A user is affected if the device is an MiiNePort E1 with firmware <=1.7, E2 <=1.3, or E3 <=1.0 AND configuration files contain unencrypted credentials or network settings that are readable in plain text.
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 dataUpdate firmware to version E1 1.8, E2 1.4, or E3 1.1 or later which encrypts configuration data. If updates are unavailable, restrict physical and network access to the device file system.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9346 — 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-9346 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