dbcve.org
Nport 5100 Series FirmwareOperating system · Moxa

CVE-2016-9369

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. Firmware can be updated over the network without authentication, which may allow remote code execution.

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 NPort series of serial-to-ethernet device servers contains a critical vulnerability allowing unauthenticated firmware updates over the network. An attacker can exploit this by sending crafted firmware update packets to the device, potentially leading to remote code execution with full control of the device.

MitigationUpdate firmware to the patched versions specified for each NPort series (2.6 for NPort 5110, 3.6 for 5130/5150, 2.8 for 5200, 3.11 for 5400, 3.7 for 5600, 1.3 for 5100A/5200A, 1.2 for M12 series, 2.4 for DT/DTL series, 1.13.11 for 6x50, v1.4 for IA5450A). If patching is not immediately possible, network-segment the devices and restrict access to management interfaces.

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 Moxa NPort device on network
    Check device IP addresses or use network scanning to identify Moxa NPort serial-to-ethernet device servers. Look for devices with HTTP services returning Moxa NPort web interface or use SNMP with Moxa OID 1.3.6.1.4.1.211.1.223 to confirm the device series.
    Affected if Device is a Moxa NPort series (5100, 5200, 5400, 5600, 5100a, P5150a, 5200a, or 5x50a1 M12)
  2. Determine firmware version via web interface
    Access the device web interface at http://[device-ip] and navigate to System Settings or Device Information page to view the firmware version. Login credentials may be required.
    Affected if Firmware version cannot be retrieved or retrieved version is <= affected threshold for that series
  3. Determine firmware version via NPort Administrator software
    Use Moxa NPort Administrator tool (or nport_admin utility) on a Windows machine on the same network to search for NPort devices. Right-click on discovered device and select 'Configure' to view firmware version.
    Affected if Firmware version matches or is below affected thresholds for the specific series
  4. Determine firmware version via console or telnet
    Connect to device via serial console or telnet to port 23 (if enabled) and use the 'show' or 'sys info' command to display firmware version information.
    Affected if Unable to retrieve version or version is in affected range
  5. Check if firmware update interface is network accessible
    Verify that HTTP/HTTPS ports (typically 80/443) or the firmware update port (5000) are open and reachable from untrusted network segments. Use 'telnet [device-ip] 80' or port scanning to confirm exposure.
    Affected if Firmware update interface is exposed to network segments that contain untrusted users

You are affected if you have a Moxa NPort device on your network with firmware version at or below the threshold for your specific series (5100 <=2.5/3.5, 5200 <=2.7, 5400 <=3.10, 5600 <=3.6, 5100a <=1.2, P5150a <=1.2, 5200a <=1.2, 5x50a1 M12 <=1.1) and the management interface is network-accessible.

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 firmware to the patched versions specified for each NPort series (2.6 for NPort 5110, 3.6 for 5130/5150, 2.8 for 5200, 3.11 for 5400, 3.7 for 5600, 1.3 for 5100A/5200A, 1.2 for M12 series, 2.4 for DT/DTL series, 1.13.11 for 6x50, v1.4 for IA5450A). If patching is not immediately possible, network-segment the devices and restrict access to management interfaces.

Recommended fix High confidence

Model-specific minimum versions: NPort 5110: 2.6+, NPort 5130/5150: 3.6+, NPort 5200: 2.8+, NPort 5400: 3.11+, NPort 5600: 3.7+, NPort 5100A/P5150A/5200A: 1.3+, NPort 5x50AI-M12 series: 1.2+, NPort 5600-8-DT/DTL: 2.4+, NPort 6x50: 1.13.11+, NPort IA5450A: v1.4+

  1. 1. Identify the exact NPort model number from the device label or web interface.
  2. 2. Determine the current firmware version by accessing the device's web interface under 'System' > 'Firmware' or using the NPort Administrator utility.
  3. 3. Download the latest firmware from the official Moxa support website (www.moxa.com/support) corresponding to your specific model series.
  4. 4. Access the device's web interface and navigate to 'System' > 'Firmware Upgrade' or use the NPort Administrator firmware upgrade function.
  5. 5. Upload the new firmware file and allow the upgrade process to complete - do not power off the device during flashing.
  6. 6. After reboot, verify the new firmware version matches the fixed version for your model (e.g., 2.6+ for 5110, 3.6+ for 5130/5150, 2.8+ for 5200, 3.11+ for 5400, 3.7+ for 5600, 1.3+ for 5100A/5200A/P5150A, 1.2+ for M12 series).
Caveat Firmware upgrades on industrial devices may reset configuration to defaults; back up current configuration before upgrading and restore after

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

Fix this in Nport 5100 Series Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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