Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-17178: An issue was discovered on Neato Botvac Connected 2.2.0 devices

37
Routine
MEDIUM 5.3MITIGATEMITIGATEMITIGATE

CVE-2018-17178 is a medium-severity flaw (CVSS 5.3) affecting botvac d4 connected firmware, botvac d6 connected firmware, botvac d5 connected firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered on Neato Botvac Connected 2.2.0 devices. They execute unauthenticated manual drive commands (sent to /bin/webserver on port 8081) if they already have an active session. Commands like forward, back, arc-left, arc-right, pivot-left, and pivot-right are executed even though the web socket replies with { "message" : "invalid authorization header" }. Without an active session, commands are still interpreted, but (except for ec

Why this priority

  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score5.3 (Medium)
Attack vectorAdjacent network
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.7% (top 48%)
CISA exploited listNo
Published2018-09-18
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: neatorobotics

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

neatorobotics botvac d4 connected firmware MITIGATE
Affected: 2.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
neatorobotics botvac d6 connected firmware MITIGATE
Affected: 2.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
neatorobotics botvac d5 connected firmware MITIGATE
Affected: 2.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
neatorobotics botvac d7 connected firmware MITIGATE
Affected: 2.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
neatorobotics botvac d3 connected firmware MITIGATE
Affected: 2.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-17178?

botvac d4 connected firmware: mitigate or apply the listed mitigation; botvac d6 connected firmware: mitigate or apply the listed mitigation; botvac d5 connected firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-17178 being exploited?

CVE-2018-17178 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-17178 affect?

CVE-2018-17178 affects botvac d4 connected firmware, botvac d6 connected firmware, botvac d5 connected firmware. Severity is medium (CVSS 5.3). An issue was discovered on Neato Botvac Connected 2.2.0 devices. They execute unauthenticated manual drive commands (sent to /bin/webserver on port 8081) if they already have an active session. Commands like forward, back, arc-left, arc-rig

How urgent is CVE-2018-17178?

Priority 37/100. Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.