dbcve.org
Nport 5100 Series FirmwareOperating system · Moxa

CVE-2016-9361

CRITICAL · 9.8 CVSS v3.1 Published 2017-02-13
Fix available
A fix is available. Upgrade to after 3.10 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An 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. Administration passwords can be retried without authenticating.

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 NPort device firmware allows unlimited password retry attempts without any rate limiting, authentication requirement, or account lockout. This enables unauthenticated attackers to conduct brute-force attacks against administrative passwords over the network.

MitigationUpdate affected NPort device firmware to the patched versions specified (2.6, 3.6, 2.8, 3.11, 3.7, 1.3, 1.2, 2.4, 1.13.11, v1.4 depending on series). If immediate patching is not possible, restrict network access to management interfaces via firewall or VLAN segmentation.

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
Nport 5100 Series FirmwareOperating system
Affected:<= 2.5<= 3.5
Nport 5200 Series FirmwareOperating system
Affected:<= 2.7
Nport 5400 Series FirmwareOperating system
Affected:<= 3.10
Nport 5600 Series FirmwareOperating system
Affected:<= 3.6
Nport 5100a Series FirmwareOperating system
Affected:<= 1.2
Nport P5150a Series FirmwareOperating system
Affected:<= 1.2
Nport 5200a Series FirmwareOperating system
Affected:<= 1.2
Nport 5x50a1 M12 Series FirmwareOperating system
Affected:<= 1.1

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
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 checks

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

  1. Identify the device model
    Check the device label, web interface header, or SNMP sysDescr for 'NPort' and the specific series number (5100, 5200, 5400, 5600, 5100a, P5150a, 5200a, or 5x50a1 M12)
    Affected if The device is a Moxa NPort series not listed in the affected products section or is a different manufacturer entirely
  2. Determine the firmware version
    Access the web-based management interface and navigate to the System Settings or Operations section to view the firmware version. Alternatively, use the console CLI command 'show firmware' or query via SNMP OID 1.3.6.1.4.1.8691.7.128
    Affected if Unable to retrieve firmware version or the device does not support firmware version reporting
  3. Compare firmware version against affected ranges
    Match your installed firmware version to the following affected ranges: NPort 5100 <= 2.5 or <= 3.5; NPort 5200 <= 2.7; NPort 5400 <= 3.10; NPort 5600 <= 3.6; NPort 5100a <= 1.2; NPort P5150a <= 1.2; NPort 5200a <= 1.2; NPort 5x50a1 M12 <= 1.1
    Affected if The installed firmware version falls within or below any of these affected version thresholds
  4. Verify network exposure of management interface
    Check firewall rules, VLAN configuration, or access control lists to determine if the NPort web management port (typically 80/443) or Telnet/SSH management ports are accessible from untrusted network segments or the internet
    Affected if Management interfaces are reachable from networks outside your trusted administrative zone

A user is affected if they have a Moxa NPort device from the listed series running firmware at or below the specified version thresholds, and that management interface is accessible from a network where unauthenticated attackers could attempt unlimited password guesses.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.10
Interim mitigation

Update affected NPort device firmware to the patched versions specified (2.6, 3.6, 2.8, 3.11, 3.7, 1.3, 1.2, 2.4, 1.13.11, v1.4 depending on series). If immediate patching is not possible, restrict network access to management interfaces via firewall or VLAN segmentation.

Recommended fix High confidence

Upgrade to the minimum fixed version for your model: 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.1

  1. 1. Identify the specific NPort model (e.g., NPort 5110, NPort 5200, etc.) from the device label or web interface
  2. 2. Check the current firmware version via the device's web console or admin interface
  3. 3. Download the latest firmware from the official Moxa website (www.moxa.com) matching your specific model
  4. 4. Back up the current device configuration through the web interface before upgrading
  5. 5. Upload and apply the firmware update via the device's admin interface, following Moxa's upgrade instructions
  6. 6. After reboot, verify the new firmware version is installed
  7. 7. Restore the configuration backup if needed
  8. 8. Confirm the web interface now properly enforces authentication on password retry attempts
Caveat Firmware upgrades may temporarily disrupt network connectivity; verify compatibility with any custom configurations before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nport 5100 Series Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9361 — 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-2016-9361 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