dbcve.org
Diqee360 FirmwareOperating system · Diqee

CVE-2018-10987

HIGH · 7.5 CVSS v3.0 Published 2018-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Dongguan Diqee Diqee360 vacuum cleaner contains an authenticated remote code execution vulnerability in the REQUEST_SET_WIFIPASSWD UDP command (command 153). An authenticated attacker can send a specially crafted UDP packet containing shell commands that get executed via the unsanitized %s parameter in '/mnt/skyeye/mode_switch.sh %s', running as root. Authentication can be achieved using the default admin password (888888).

MitigationUsers should immediately change the default admin password from 888888 to a strong unique password and place IoT devices on isolated network segments. Vendors should release a firmware patch that implements proper input validation and avoids shell execution of user-controlled parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Diqee360 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Diqee Diqee360 vacuum cleaner on your network
    Check your network device inventory, DHCP lease tables, or perform network scanning to identify devices with manufacturer OUI matching Dongguan Diqee or model identifiers matching Diqee360. Inspect the device label or web interface for model information.
    Affected if The device is a Diqee Diqee360 vacuum cleaner and is present on your network.
  2. Verify if default admin password is still in use
    Attempt to authenticate to the device admin interface (typically HTTP on port 80/8080) using the default credentials admin:888888. If authentication succeeds, the default password has not been changed.
    Affected if The default admin password (888888) is still active and allows authentication.
  3. Check network exposure of the UDP management service
    Perform a UDP port scan against the device IP address on common IoT management ports (typically 20002-20004 range). Verify if the device UDP service accepting command 153 is reachable from untrusted network segments.
    Affected if The device UDP management service is accessible from a network segment that is not isolated from untrusted users.
  4. Confirm firmware version is unpatched
    Access the device admin interface and check the firmware version information. Compare against any available firmware update history from the vendor.
    Affected if The device runs any firmware version (all versions per vendor advisory are affected).

You are affected if you have a Diqee Diqee360 vacuum cleaner on your network using the default admin password (888888) with its UDP management service exposed to untrusted network segments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should immediately change the default admin password from 888888 to a strong unique password and place IoT devices on isolated network segments. Vendors should release a firmware patch that implements proper input validation and avoids shell execution of user-controlled parameters.

Fix this in Diqee360 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10987 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data