Skip to main content
No exploitation reported

CVE-2020-10271

No exploitation reported by the sources we read.

  • Published2020-06-24
  • WeaknessCWE-668

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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).

Timeline

dates in UTC
  1. 2020-06-2405:15CVE publishedNVD

Versions per branch

NVD
Aliasrobotics mir100 firmwareversion to verify
BranchAffectedFixed in
2.8≤ 2.8.1.1no fix published
Aliasrobotics mir1000 firmwareversion to verify
BranchAffectedFixed in
2.8≤ 2.8.1.1no fix published
Aliasrobotics mir200 firmwareversion to verify
BranchAffectedFixed in
2.8≤ 2.8.1.1no fix published

7 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-21-280-02 CISA2 known affected

    Mobile Industrial Robots Vehicles and MiR Fleet Software

    MiR100 MiR200 MiR250 MiR500 MiR1000 in MiR Robot Software: versions prior to 2.10.2.1 · MiR Fleet in MiR Fleet Software: versions prior to 2.10.2.1

Full record on NVD

Fix

  1. Mitigation from the vendor CISA ICSA-21-280-02 · 2 productsMiR recommends users upgrade affected products to the latest version. New software versions can be found on the MiR Distributor portal (login required).
  2. Mitigation from the vendor CISA ICSA-21-280-02 · 2 productsFor more information, refer to MiR's security advisories page.
  3. Mitigation from the vendor CISA ICSA-21-280-02 · 2 productsMiR instructs customers to explicitly change default credentials upon configuring the robots, including default SSID and password to the WiFi access point.

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.19.8read 2026-10-23
  • CNACVSS 3.010known since 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • CNAweakness (CWE)CWE-668known since 2026-10-23
  • NVDweakness (CWE)CWE-668read 2026-10-23
  • FIRST EPSSEPSS score1.8 %2026-11-08
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2020-06-24
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-w563-xmmw-pqwr

Frequently asked questions

What is CVE-2020-10271?

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).

Is CVE-2020-10271 actively exploited?

Active exploitation of CVE-2020-10271 has not been confirmed. Its EPSS score was 1.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-10271?

CVE-2020-10271 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record