MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computational graph to all network interfaces, wireless and wired. This is the result of a bad set up and can be mitigated by appropriately configuring ROS and/or applying custom patches as appropriate. Currently, the ROS computational graph can be accessed fully from the wired exposed ports. In combination with other flaws such as CVE-2020-10269, the computation graph can also be fetched and interacted from wireless networks. This allows a malicious operator to take control of the ROS logic and correspondingly, the complete robot given that MiR's operations are centered around the framework (ROS).
Conclusion & alert: CVE-2020-10271 is rated High Exploit Risk (74.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.44%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
| EDB-ID | Source | Kind | Published | Link |
|---|---|---|---|---|
| — | nvd_ref | exploit_tag | Exploit-DB ↗ |
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2025-03-30 | 0.85% | 0.44% | -0.41% |
| 2 | 2025-03-29 | 0.44% | 0.85% | +0.41% |
| 3 | 2025-03-17 | — | 0.44% | — |
Full EPSS history (11 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 9.8 | 3.1 | CRITICAL |
|
3.9 | 5.9 | [email protected] |
| 10.0 | 3.0 | CRITICAL |
|
3.9 | 6.0 | [email protected] |
| 5.0 | 2.0 | MEDIUM |
|
10.0 | 2.9 | [email protected] |
| Vendor | Product | Version | Raw CPE |
|---|---|---|---|
| aliasrobotics | mir100_firmware | <= 2.8.1.1 | cpe:2.3:o:aliasrobotics:mir100_firmware:*:*:*:*:*:*:*:* |
| aliasrobotics | mir200_firmware | <= 2.8.1.1 | cpe:2.3:o:aliasrobotics:mir200_firmware:*:*:*:*:*:*:*:* |
| aliasrobotics | mir250_firmware | <= 2.8.1.1 | cpe:2.3:o:aliasrobotics:mir250_firmware:*:*:*:*:*:*:*:* |
| aliasrobotics | mir500_firmware | <= 2.8.1.1 | cpe:2.3:o:aliasrobotics:mir500_firmware:*:*:*:*:*:*:*:* |
| aliasrobotics | mir1000_firmware | <= 2.8.1.1 | cpe:2.3:o:aliasrobotics:mir1000_firmware:*:*:*:*:*:*:*:* |
| mobile-industrial-robotics | er200_firmware | <= 2.8.1.1 | cpe:2.3:o:mobile-industrial-robotics:er200_firmware:*:*:*:*:*:*:*:* |
| enabled-robotics | er-lite_firmware | <= 2.8.1.1 | cpe:2.3:o:enabled-robotics:er-lite_firmware:*:*:*:*:*:*:*:* |
| enabled-robotics | er-flex_firmware | <= 2.8.1.1 | cpe:2.3:o:enabled-robotics:er-flex_firmware:*:*:*:*:*:*:*:* |
| enabled-robotics | er-one_firmware | <= 2.8.1.1 | cpe:2.3:o:enabled-robotics:er-one_firmware:*:*:*:*:*:*:*:* |
| uvd-robots | uvd_robots_firmware | <= 2.8.1.1 | cpe:2.3:o:uvd-robots:uvd_robots_firmware:*:*:*:*:*:*:*:* |
| URL | Tags |
|---|---|
| https://github.com/aliasrobotics/RVD/issues/2555 | Exploit Third Party Advisory |