CVE-2020-10273: MiR controllers across firmware versions 2.8.1.1 and before do not encrypt or protect in any way the intellect
46
This month
HIGH 7.5REMOTEUPGRADEUPGRADEUPGRADE
CVE-2020-10273 is a high-severity flaw (CVSS 7.5) affecting mir100 firmware, mir200 firmware, mir250 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
MiR controllers across firmware versions 2.8.1.1 and before do not encrypt or protect in any way the intellectual property artifacts installed in the robots. This flaw allows attackers with access to the robot or the robot network (while in combination with other flaws) to retrieve and easily exfiltrate all installed intellectual property and data.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
Published CVE record published
Updated Record last modified
aliasrobotics mir100 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
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.
aliasrobotics mir200 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
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.
aliasrobotics mir250 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
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.
aliasrobotics mir500 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
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.
aliasrobotics mir1000 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
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.
mobile-industrial-robotics er200 firmware UPGRADE
Affected: <= 2.8.1.1
Fixed in: newer than 2.8.1.1
Safe to downgrade to: no unaffected older release
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 sourceNVD · 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-2020-10273?
mir100 firmware: upgrade to newer than 2.8.1.1; mir200 firmware: upgrade to newer than 2.8.1.1; mir250 firmware: upgrade to newer than 2.8.1.1. Exact commands for each OS are on this page.
Is CVE-2020-10273 being exploited?
CVE-2020-10273 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-2020-10273 affect?
CVE-2020-10273 affects mir100 firmware, mir200 firmware, mir250 firmware. Severity is high (CVSS 7.5). MiR controllers across firmware versions 2.8.1.1 and before do not encrypt or protect in any way the intellectual property artifacts installed in the robots. This flaw allows attackers with access to the robot or the robot network (while in
How urgent is CVE-2020-10273?
Priority 46/100. High severity; Remotely exploitable, no login, no user action
Related CVEs
CVE-2020-10280HIGH 7.5UPGRADEMITIGATE The Apache server on port 80 that host the web interface is vulnerable to a DoS by spamming incomplete HTTP he
CVE-2020-10279CRITICAL 9.8UPGRADEUPGRADE MiR robot controllers (central computation unit) makes use of Ubuntu 16.04.2 an operating system, Thought for
CVE-2020-10278MEDIUM 4.6UPGRADEUPGRADE The BIOS onboard MiR's Computer is not protected by password, therefore, it allows a Bad Operator to modify se
CVE-2020-10277MEDIUM 6.4UPGRADEMITIGATE There is no mechanism in place to prevent a bad operator to boot from a live OS image, this can lead to extrac
CVE-2020-10276CRITICAL 9.8UPGRADEMITIGATE The password for the safety PLC is the default and thus easy to find (in manuals, etc.)
PatchTheCVE