# CVE-2018-18881: Denial of service in n/a

> An authenticated user can cause a denial of service by configuring invalid network settings, requiring a physical factory reset to recover.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-352m-3444-89q4

## What is CVE-2018-18881?

CVE-2018-18881 is a medium-severity denial of service vulnerability in n/a, published on 17 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Denial of Service (DOS) issue was discovered in ControlByWeb X-320M-I Web-Enabled Instrumentation-Grade Data Acquisition module 1.05 with firmware revision v1.05. An authenticated user can configure invalid network settings, stopping TCP based communications to the device. A physical factory reset is required to restore the device to an operational state.

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

It affects 1 product.


Products: Controlbyweb X-320m-I Firmware.

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

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

## Is CVE-2018-18881 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18882](https://insights.sbomify.com/CVE-2018-18882/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18881 is a medium-severity denial of service vulnerability in n/a, published on 17 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18881 in the wild and no public exploit code.

Affected product: n/a. 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-18881/ (Markdown: https://insights.sbomify.com/CVE-2018-18881/index.md)
```

## Sources

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

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