CVE-2016-9366
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 NPort 5110 versions prior to 2.6, NPort 5130/5150 Series versions prior to 3.6, NPort 5200 Series versions prior to 2.8, NPort 5400 Series versions prior to 3.11, NPort 5600 Series versions prior to 3.7, NPort 5100A Series & NPort P5150A versions prior to 1.3, NPort 5200A Series versions prior to 1.3, NPort 5150AI-M12 Series versions prior to 1.2, NPort 5250AI-M12 Series versions prior to 1.2, NPort 5450AI-M12 Series versions prior to 1.2, NPort 5600-8-DT Series versions prior to 2.4, NPort 5600-8-DTL Series versions prior to 2.4, NPort 6x50 Series versions prior to 1.13.11, NPort IA5450A versions prior to v1.4. An attacker can freely use brute force to determine parameters needed to bypass authentication.
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 NPort serial-to-Ethernet converters contain an authentication bypass vulnerability allowing attackers to brute force parameters needed to bypass authentication, enabling unauthenticated access to the device and potentially the connected serial devices and network.
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<= 2.5<= 3.5<= 2.7<= 3.10<= 3.6<= 1.2<= 1.2<= 1.2<= 1.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 NPort device modelLocate the model number label on the physical device or check the device's web interface or console for the model designation (e.g., NPort 5100, 5200, 5400, 5600, 5100a, P5150a, 5200a, or 5x50a1 M12)Affected if The model is any of the NPort 5100, 5200, 5400, 5600, 5100a, P5150a, 5200a, or 5x50a1 M12 series
-
Determine the installed firmware versionAccess the device web interface and navigate to the Firmware or System Information page, or use the NPort Administration Suite software or console command to retrieve the firmware versionAffected if The firmware version matches or is below the affected version for that specific model series
-
Verify network exposure of the management interfaceCheck if the device web interface (HTTP/HTTPS) or management ports are accessible from untrusted networks by reviewing firewall rules, NAT configurations, or network segmentationAffected if The management interface is reachable from networks outside the trusted internal segment without proper access controls
A user is affected if they have a vulnerable NPort model (5100, 5200, 5400, 5600, 5100a, P5150a, 5200a, or 5x50a1 M12 series) running firmware at or below the affected version for that model, and the device management interface is exposed to network segments where untrusted users could attempt authentication bypass attacks.
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.
dbcve · scopedUpgrade all affected NPort device models to their respective fixed firmware versions (2.6, 3.6, 2.8, 3.11, 3.7, 1.3, 1.2, 2.4, 1.13.11, v1.4 depending on model series) or isolate devices behind a firewall if upgrades are not immediately feasible.
Upgrade to firmware version v2.6 or later for NPort 5110; v3.6+ for NPort 5130/5150; v2.8+ for NPort 5200; v3.11+ for NPort 5400; v3.7+ for NPort 5600; v1.3+ for NPort 5100A/5200A/P5150A; v1.2+ for M12 series; v2.4+ for 5600-8-DT/DTL; v1.13.11+ for 6x50 series; v1.4+ for IA5450A
- 1. Identify the exact NPort model number and current firmware version from the device web interface or administration console
- 2. Download the latest firmware for your specific NPort model from the official Moxa website (www.moxa.com)
- 3. Review the firmware release notes for any configuration or compatibility considerations
- 4. Create a backup of the current device configuration
- 5. Connect to the device via Ethernet and access the administration web interface
- 6. Navigate to the Firmware Upgrade or System Maintenance section
- 7. Upload and apply the appropriate fixed firmware version: NPort 5110 to v2.6+, NPort 5130/5150 to v3.6+, NPort 5200 to v2.8+, NPort 5400 to v3.11+, NPort 5600 to v3.7+, NPort 5100A/P5150A to v1.3+, NPort 5200A to v1.3+, NPort 5x50AI-M12 series to v1.2+, NPort 5600-8-DT/DTL to v2.4+, NPort 6x50 to v1.13.11+, NPort IA5450A to v1.4+
- 8. Wait for the firmware upload and reboot process to complete
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9366 — 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-9366 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