# CVE-2018-10632: Denial of service in NPort 5210, 5230, and 5232

> A malicious actor can cause a denial-of-service condition on Moxa NPort serial device servers by requesting excessive resources.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g28g-qq9m-986c

## What is CVE-2018-10632?

CVE-2018-10632 is a high-severity denial of service vulnerability in Moxa NPort 5210, 5230, and 5232, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Moxa NPort 5210, 5230, and 5232 versions 2.9 build 17030709 and prior, the amount of resources requested by a malicious actor are not restricted, allowing for a denial-of-service condition.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2018-10632?

It affects 3 products.


Products: Moxa Nport 5210 Firmware, Moxa Nport 5230 Firmware, Moxa Nport 5232 Firmware.

## How do I fix CVE-2018-10632?

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

## Is CVE-2018-10632 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10632 and fix it if it is affected.

What it is: CVE-2018-10632 is a high-severity denial of service vulnerability in Moxa NPort 5210, 5230, and 5232, published on 24 Jul 2018. 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-2018-10632 in the wild and no public exploit code.

Affected product: Moxa NPort 5210, 5230, and 5232. 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-2018-10632/ (Markdown: https://insights.sbomify.com/CVE-2018-10632/index.md)
```

## Sources

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

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