CVE-2020-10271: RVD#2555: MiR ROS computational graph is exposed to all network interfaces, including poorly secured wireless networks and open wired ones
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Jun 24, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-668
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CNA vs NVD score
- NVD
- 9.8
- CNA · Alias
- 10.0
- 0.2 point gap
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| aliasrobotics | mir100 firmware | cpe:2.3:o:aliasrobotics:mir100_firmware |
| aliasrobotics | mir100 | cpe:2.3:h:aliasrobotics:mir100 |
| aliasrobotics | mir200 firmware | cpe:2.3:o:aliasrobotics:mir200_firmware |
| aliasrobotics | mir200 | cpe:2.3:h:aliasrobotics:mir200 |
| aliasrobotics | mir250 firmware | cpe:2.3:o:aliasrobotics:mir250_firmware |
| aliasrobotics | mir250 | cpe:2.3:h:aliasrobotics:mir250 |
| aliasrobotics | mir500 firmware | cpe:2.3:o:aliasrobotics:mir500_firmware |
| aliasrobotics | mir500 | cpe:2.3:h:aliasrobotics:mir500 |
| aliasrobotics | mir1000 firmware | cpe:2.3:o:aliasrobotics:mir1000_firmware |
| aliasrobotics | mir1000 | cpe:2.3:h:aliasrobotics:mir1000 |
| mobile-industrial-robotics | er200 firmware | cpe:2.3:o:mobile-industrial-robotics:er200_firmware |
| mobile-industrial-robotics | er200 | cpe:2.3:h:mobile-industrial-robotics:er200 |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- aliasrobotics mir100 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir1000 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir200 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir250 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir500 firmwareup to 2.8.1.1 inclusive
- enabled-robotics er-flex firmwareup to 2.8.1.1 inclusive
- enabled-robotics er-lite firmwareup to 2.8.1.1 inclusive
- enabled-robotics er-one firmwareup to 2.8.1.1 inclusive
- mobile-industrial-robotics er200 firmwareup to 2.8.1.1 inclusive
- uvd-robots uvd robots firmwareup to 2.8.1.1 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Alias). Independent of NVD's CPE analysis and usually ahead of it.
Mobile Industrial Robots A/S MiR100
- v2.8.1.1 and beforeaffected
Same product
aliasrobotics: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-10272RVD#2554: MiR ROS computational graph presents no authentication mechanisms40Plan
- CVE-2020-10279RVD#2569: Insecure operating system defaults in MiR robots39Monitor
- CVE-2020-10270RVD#2557: Hardcoded Credentials on MiRX00 Control Dashboard39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-10269Jun 24, 2020 · RVD#2566: Hardcoded Credentials on MiRX00 wireless Access Point39Monitor
- Later →CVE-2020-10273Jun 24, 2020 · RVD#2560: Unprotected intellectual property in Mobile Industrial Robots (MiR) controllers30Monitor
- Later →CVE-2020-10278Jun 24, 2020 · RVD#2561: Unprotected BIOS allows user to boot from live OS image.18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-668 · Exposure of Resource to Wrong SphereCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.