# CVE-2018-17177: Hardcoded credentials in n/a

> Attackers can decrypt sensitive robot logs from USB sticks using a hardcoded RC4 password, exposing internal event data and core dumps.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m5xh-jxq3-g8gc

## What is CVE-2018-17177?

CVE-2018-17177 is a low-severity vulnerability in n/a, published on 18 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 6 products.


Products: Neatorobotics Botvac 85 Firmware, Neatorobotics Botvac D3 Connected Firmware, Neatorobotics Botvac D4 Connected Firmware, Neatorobotics Botvac D5 Connected Firmware, Neatorobotics Botvac D6 Connected Firmware, Neatorobotics Botvac D7 Connected Firmware.

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

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

## Is CVE-2018-17177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17177 is a low-severity vulnerability in n/a, published on 18 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17177 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-17177/ (Markdown: https://insights.sbomify.com/CVE-2018-17177/index.md)
```

## Sources

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

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