# CVE-2020-10279: RVD#2569: Insecure operating system defaults in MiR robots

> Insecure Ubuntu defaults in MiR robot controllers allow attackers to escalate privileges via race conditions and cause denial of service.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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-ghmv-6mj4-m43m

## What is CVE-2020-10279?

CVE-2020-10279 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

MiR robot controllers (central computation unit) makes use of Ubuntu 16.04.2 an operating system, Thought for desktop uses, this operating system presents insecure defaults for robots. These insecurities include a way for users to escalate their access beyond what they were granted via file creation, access race conditions, insecure home directory configurations and defaults that facilitate Denial of Service (DoS) attacks.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-1188 (Initialization of a Resource with an Insecure Default), CWE-276 (Incorrect Default Permissions)

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

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

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

## Is CVE-2020-10279 being exploited?

There is no known exploitation of CVE-2020-10279 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-10269](https://insights.sbomify.com/CVE-2020-10269/): RVD#2566: Hardcoded Credentials on MiRX00 wireless Access Point (critical 9.8)
- [CVE-2020-10270](https://insights.sbomify.com/CVE-2020-10270/): RVD#2557: Hardcoded Credentials on MiRX00 Control Dashboard (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-10279 and fix it if it is affected.

What it is: CVE-2020-10279 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-10279 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-10279/ (Markdown: https://insights.sbomify.com/CVE-2020-10279/index.md)
```

## Sources

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

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