dbcve.org
Nport 5100 Series FirmwareOperating system · Moxa

CVE-2016-9363

HIGH · 7.3 CVSS v3.1 Published 2017-02-13
Fix available
A fix is available. Upgrade to after 3.10 or later.
See remediation →
82/100
Remediation priority · High
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. Buffer overflow vulnerability may allow an unauthenticated attacker to remotely execute arbitrary code.

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

A buffer overflow vulnerability in Moxa NPort device firmware allows unauthenticated remote attackers to execute arbitrary code. The flaw exists in multiple NPort series (5110, 5130/5150, 5200, 5400, 5600, 5100A, 5200A, 5150AI-M12, 5250AI-M12, 5450AI-M12, 5600-8-DT, 5600-8-DTL, 6x50, IA5450A) prior to their respective version thresholds.

MitigationUpdate affected NPort device firmware to the patched versions specified (NPort 5110: 2.6, NPort 5130/5150: 3.6, NPort 5200: 2.8, NPort 5400: 3.11, NPort 5600: 3.7, 5100A/P5150A: 1.3, 5200A: 1.3, 5150AI-M12: 1.2, 5250AI-M12: 1.2, 5450AI-M12: 1.2, 5600-8-DT/DTL: 2.4, 6x50: 1.13.11, IA5450A: v1.4) or later versions.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 NPort model
    Access the device web interface or console and locate the model number (e.g., NPort 5110, 5130, 5200, 5400, 5600, 5100A, 5200A, etc.) in the system status or device information page
    Affected if The model is one of the affected series: 5110, 5130/5150, 5200, 5400, 5600, 5100A, P5150A, 5200A, 5150AI-M12, 5250AI-M12, 5450AI-M12, 5600-8-DT, 5600-8-DTL, 6x50, or IA5450A
  2. Retrieve the firmware version
    In the device web interface, go to System Settings or Device Status to view the firmware version. Alternatively, use the console/Telnet/SSH and run the command to display firmware version (refer to device manual for specific command)
    Affected if The firmware version cannot be determined or is not visible in the expected location
  3. Compare firmware version against affected ranges
    Match the installed firmware version to the known vulnerable version thresholds: NPort 5100 Series <= 2.5 or <= 3.5; NPort 5200 Series <= 2.7; NPort 5400 Series <= 3.10; NPort 5600 Series <= 3.6; NPort 5100A/P5150A <= 1.2; NPort 5200A <= 1.2; NPort 5x50a1 M12 Series <= 1.1
    Affected if The installed firmware version falls within or below the vulnerable thresholds for your specific model

The device is affected if it is an NPort model from the listed series AND its firmware version is at or below the version threshold for that series.

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.

From vendor data
Upgrade available Upgrade to a release after 3.10
Interim mitigation

Update affected NPort device firmware to the patched versions specified (NPort 5110: 2.6, NPort 5130/5150: 3.6, NPort 5200: 2.8, NPort 5400: 3.11, NPort 5600: 3.7, 5100A/P5150A: 1.3, 5200A: 1.3, 5150AI-M12: 1.2, 5250AI-M12: 1.2, 5450AI-M12: 1.2, 5600-8-DT/DTL: 2.4, 6x50: 1.13.11, IA5450A: v1.4) or later versions.

Fix this in Nport 5100 Series Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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