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

> An authenticated attacker can execute arbitrary commands as root on Diqee360 vacuum cleaners via a crafted UDP packet, potentially using default credentials.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 5 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8337-gx57-xm96

## What is CVE-2018-10987?

CVE-2018-10987 is a high-severity command injection vulnerability in n/a, published on 5 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Dongguan Diqee Diqee360 devices. The affected vacuum cleaner suffers from an authenticated remote code execution vulnerability. An authenticated attacker can send a specially crafted UDP packet, and execute commands on the vacuum cleaner as root. The bug is in the function REQUEST_SET_WIFIPASSWD (UDP command 153). A crafted UDP packet runs "/mnt/skyeye/mode_switch.sh %s" with an attacker controlling the %s variable. In some cases, authentication can be achieved with the default password of 888888 for the admin account.

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

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

It affects 1 product.


Products: Diqee Diqee360 Firmware.

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

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

## Is CVE-2018-10987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10988](https://insights.sbomify.com/CVE-2018-10988/): Code injection in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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