# CVE-2016-9363: Memory corruption in Moxa NPort

> Unauthenticated attackers can remotely execute arbitrary code via a buffer overflow in Moxa NPort serial servers.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-v88g-7m4q-fv37

## What is CVE-2016-9363?

CVE-2016-9363 is a high-severity memory corruption vulnerability in Moxa NPort, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2016-9363?

It affects 10 products.


Products: Moxa Nport 5100 Series Firmware, Moxa Nport 5100a Series Firmware, Moxa Nport 5200 Series Firmware, Moxa Nport 5200a Series Firmware, Moxa Nport 5400 Series Firmware, Moxa Nport 5600-8-Dtl Series Firmware, Moxa Nport 5600 Series Firmware, Moxa Nport 5x50a1-M12 Series Firmware, Moxa Nport 6100 Series Firmware, Moxa Nport P5150a Series Firmware.

## How do I fix CVE-2016-9363?

No fix has been published for CVE-2016-9363 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-9363 being exploited?

There is no known exploitation of CVE-2016-9363 in the wild and no public exploit code.

## Other vulnerabilities in Moxa NPort

- [CVE-2016-9361](https://insights.sbomify.com/CVE-2016-9361/): Auth bypass in Moxa NPort (critical 9.8)
- [CVE-2016-9366](https://insights.sbomify.com/CVE-2016-9366/): Auth bypass in Moxa NPort (critical 9.8)
- [CVE-2016-9369](https://insights.sbomify.com/CVE-2016-9369/): Auth bypass in Moxa NPort (critical 9.8)
- [CVE-2016-9365](https://insights.sbomify.com/CVE-2016-9365/): Cross-site request forgery in Moxa NPort (high 8.8)
- [CVE-2016-9367](https://insights.sbomify.com/CVE-2016-9367/): Denial of service in Moxa NPort (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9363 and fix it if it is affected.

What it is: CVE-2016-9363 is a high-severity memory corruption vulnerability in Moxa NPort, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-9363 in the wild and no public exploit code.

Affected product: Moxa NPort. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-9363/ (Markdown: https://insights.sbomify.com/CVE-2016-9363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-9363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-9363
- OSV: https://osv.dev/vulnerability/CVE-2016-9363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-9363/
Summaries are generated and may contain mistakes; the official description above is the record.