An issue was discovered on Neato Botvac Connected 2.2.0 devices.
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 eco-on and eco-off) have no effect, since without active driving, a driving direction does not change anything.
- Published
- Sep 18, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 50th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| neatorobotics | botvac d4 connected firmware | cpe:2.3:o:neatorobotics:botvac_d4_connected_firmware |
| neatorobotics | botvac d4 connected | cpe:2.3:h:neatorobotics:botvac_d4_connected |
| neatorobotics | botvac d6 connected firmware | cpe:2.3:o:neatorobotics:botvac_d6_connected_firmware |
| neatorobotics | botvac d6 connected | cpe:2.3:h:neatorobotics:botvac_d6_connected |
| neatorobotics | botvac d5 connected firmware | cpe:2.3:o:neatorobotics:botvac_d5_connected_firmware |
| neatorobotics | botvac d5 connected | cpe:2.3:h:neatorobotics:botvac_d5_connected |
| neatorobotics | botvac d7 connected firmware | cpe:2.3:o:neatorobotics:botvac_d7_connected_firmware |
| neatorobotics | botvac d7 connected | cpe:2.3:h:neatorobotics:botvac_d7_connected |
| neatorobotics | botvac d3 connected firmware | cpe:2.3:o:neatorobotics:botvac_d3_connected_firmware |
| neatorobotics | botvac d3 connected | cpe:2.3:h:neatorobotics:botvac_d3_connected |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- neatorobotics botvac d3 connected firmware2.2.0
- neatorobotics botvac d4 connected firmware2.2.0
- neatorobotics botvac d5 connected firmware2.2.0
- neatorobotics botvac d6 connected firmware2.2.0
- neatorobotics botvac d7 connected firmware2.2.0
Same product
neatorobotics: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17176A replay issue was discovered on Neato Botvac Connected 2.2.0 devices.30Monitor
- CVE-2018-20785Secure boot bypass and memory extraction can be achieved on Neato Botvac Connected 2.2.0 devices.29Monitor
- CVE-2018-17177An issue was discovered on Neato Botvac Connected 2.2.0 and Botvac 85 1.2.1 devices.9Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.