CVE-2018-17177: An issue was discovered on Neato Botvac Connected 2.2.0 and Botvac 85 1.2.1 devices

Routine

LOW 2.4MITIGATEMITIGATEMITIGATE

CVE-2018-17177 is a low-severity flaw (CVSS 2.4) 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 and Botvac 85 1.2.1 devices. Static encryption is used for the copying of so-called "black box" logs (event logs and core dumps) to a USB stick. These logs are RC4-encrypted with a 9-character password of *^JEd4W!I that is obfuscated by hiding it within a custom /bin/rc4_crypt binary.

Why this priority

Public exploit reference

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

Risk facts

CVSS score	2.4 (Low)
Attack vector	Physical
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-326
Published	2018-09-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: neatorobotics

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

Am I affected?

Timeline

2018-09-18 18:29 UTCPublished CVE record published
2026-06-17 01:45 UTCUpdated Record last modified

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.

neatorobotics botvac 85 firmware MITIGATE

Affected: 1.2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2.1

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-17177?

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-17177 being exploited?

CVE-2018-17177 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-17177 affect?

CVE-2018-17177 affects botvac d4 connected firmware, botvac d6 connected firmware, botvac d5 connected firmware. Severity is low (CVSS 2.4). An issue was discovered on Neato Botvac Connected 2.2.0 and Botvac 85 1.2.1 devices. Static encryption is used for the copying of so-called "black box" logs (event logs and core dumps) to a USB stick. These logs are RC4-encrypted with a 9-c

How urgent is CVE-2018-17177?

Priority 15/100. Public exploit reference

Related CVEs

CVE-2018-20785 HIGH 7.4 MITIGATE MITIGATE Secure boot bypass and memory extraction can be achieved on Neato Botvac Connected 2.2.0 devices
CVE-2018-17178 MEDIUM 5.3 MITIGATE MITIGATE An issue was discovered on Neato Botvac Connected 2.2.0 devices
CVE-2018-17176 HIGH 7.5 MITIGATE MITIGATE A replay issue was discovered on Neato Botvac Connected 2.2.0 devices

References

← Back to latest CVEs