# CVE-2020-10270: RVD#2557: Hardcoded Credentials on MiRX00 Control Dashboard

> Attackers can remotely control MiR robots using hardcoded default credentials on the control dashboard, enabling unauthorized access and potential manipulation.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3vvj-p2p8-pchq

## What is CVE-2020-10270?

CVE-2020-10270 is a critical vulnerability in Mobile Industrial Robots A/S MiR100, published on 24 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out of the wired and wireless interfaces within MiR100, MiR200 and other vehicles from the MiR fleet, it's possible to access the Control Dashboard on a hardcoded IP address. Credentials to such wireless interface default to well known and widely spread users (omitted) and passwords (omitted). This information is also available in past User Guides and manuals which the vendor distributed. This flaw allows cyber attackers to take control of the robot remotely and make use of the default user interfaces MiR has created, lowering the complexity of attacks and making them available to entry-level attackers. More elaborated attacks can also be established by clearing authentication and sending network requests directly. We have confirmed this flaw in MiR100 and MiR200 but according to the vendor, it might also apply to MiR250, MiR500 and MiR1000.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2020-10270?

It affects 10 products.


Products: Aliasrobotics Mir1000 Firmware, Aliasrobotics Mir100 Firmware, Aliasrobotics Mir200 Firmware, Aliasrobotics Mir250 Firmware, Aliasrobotics Mir500 Firmware, Enabled-Robotics Er-Flex Firmware, Enabled-Robotics Er-Lite Firmware, Enabled-Robotics Er-One Firmware, Mobile-Industrial-Robotics Er200 Firmware, Uvd-Robots Uvd Robots Firmware.

## How do I fix CVE-2020-10270?

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

## Is CVE-2020-10270 being exploited?

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

## Other vulnerabilities in Mobile Industrial Robots A/S MiR100

- [CVE-2020-10271](https://insights.sbomify.com/CVE-2020-10271/): Misconfiguration in MiR100 (critical 10.0)
- [CVE-2020-10272](https://insights.sbomify.com/CVE-2020-10272/): RVD#2554: MiR ROS computational graph presents no authentication mechanisms (critical 10.0)
- [CVE-2020-10279](https://insights.sbomify.com/CVE-2020-10279/): RVD#2569: Insecure operating system defaults in MiR robots (critical 10.0)
- [CVE-2020-10269](https://insights.sbomify.com/CVE-2020-10269/): RVD#2566: Hardcoded Credentials on MiRX00 wireless Access Point (critical 9.8)
- [CVE-2020-10273](https://insights.sbomify.com/CVE-2020-10273/): RVD#2560: Unprotected intellectual property in Mobile Industrial Robots (MiR) controllers (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10270 and fix it if it is affected.

What it is: CVE-2020-10270 is a critical vulnerability in Mobile Industrial Robots A/S MiR100, published on 24 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10270 in the wild and no public exploit code.

Affected product: Mobile Industrial Robots A/S MiR100. 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-2020-10270/ (Markdown: https://insights.sbomify.com/CVE-2020-10270/index.md)
```

## Sources

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

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