# CVE-2018-18638: Command injection in n/a

> Network attackers can execute arbitrary commands on Neato Botvac Connected robots via shell metacharacters in the NTP field of the setup API.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-96cj-c95w-hg9m

## What is CVE-2018-18638?

CVE-2018-18638 is a high-severity command injection vulnerability in n/a, published on 24 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability in the setup API in the Neato Botvac Connected 2.2.0 allows network attackers to execute arbitrary commands via shell metacharacters in the ntp field within JSON data to the /robot/initialize endpoint.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Neatorobotics Botvac Connected Firmware.

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

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

## Is CVE-2018-18638 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19442](https://insights.sbomify.com/CVE-2018-19442/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-20785](https://insights.sbomify.com/CVE-2018-20785/): Security feature bypass in n/a (high 7.4)
- [CVE-2018-19441](https://insights.sbomify.com/CVE-2018-19441/): Weak cryptography in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18638 is a high-severity command injection vulnerability in n/a, published on 24 Oct 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-18638 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-18638/ (Markdown: https://insights.sbomify.com/CVE-2018-18638/index.md)
```

## Sources

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

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