CVE-2020-10272
What it is
MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computational graph without any sort of authentication. This allows attackers with access to the internal wireless and wired networks to take control of the robot seamlessly. In combination with CVE-2020-10269 and CVE-2020-10271, this flaw allows malicious actors to command the robot at desire.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 2.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.5% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 2.5% · EPSS, next 30 days
- Weakness
- CWE-306 · Missing authentication
- Record status
- Modified
Affected
- Aliasrobotics mir100 Firmware ≤ 2.8.1.1
- Aliasrobotics mir200 Firmware ≤ 2.8.1.1
- Aliasrobotics mir250 Firmware ≤ 2.8.1.1
- Aliasrobotics mir500 Firmware ≤ 2.8.1.1
- Aliasrobotics mir1000 Firmware ≤ 2.8.1.1
- mobile-industrial-robotics er200 Firmware ≤ 2.8.1.1
- enabled-robotics er-lite Firmware ≤ 2.8.1.1
- enabled-robotics er-flex Firmware ≤ 2.8.1.1
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2020-10272.md and follow it. Check whether this project is affected by CVE-2020-10272. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
