Security readout for executives and security teams
Plain-English summary
MiR100 robots running affected firmware can accept REST API tokens derived from publicly known default web credentials. An attacker already on the network could use this weakness to access the robot API and read, modify, or delete data. Sources do not show active exploitation or a named vendor fix.
Executive priority
Treat as urgent for any deployed MiR100 fleet. Prioritize inventory, network restriction, credential review, and vendor guidance because compromise could affect robot data integrity and availability.
Technical view
CVE-2020-10275 affects Mobile Industrial Robots MiR100 v2.8.1.1 and earlier. REST API access tokens are predictably derived from web interface credentials, creating a critical authentication weakness. The CVSS 3.0 score is 9.8 with network attack vector and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to Mobile Industrial Robots MiR100 v2.8.1.1 and earlier, especially where the REST API is reachable from internal or poorly segmented networks.
Exploitation context
The provided sources state an unauthorized attacker inside the network can compute valid REST API tokens from default credentials. KEV is false, and no cited source confirms active exploitation.
Researcher notes
Evidence is strong for affected product, version range, token weakness, and impact. Evidence is incomplete for vendor patch availability, real-world exploitation, and broader affected models. Do not generalize beyond MiR100 without additional sources.
Mitigation direction
- Identify all MiR100 robots and firmware versions.
- Check Mobile Industrial Robots guidance for fixed firmware or official mitigations.
- Restrict REST API access to trusted management hosts only.
- Remove or change default credentials where supported.
- Segment robot networks from user, guest, and internet-facing networks.
Validation and detection
- Confirm whether any MiR100 runs v2.8.1.1 or earlier.
- Verify REST API endpoints are not reachable from untrusted internal networks.
- Review whether default web credentials remain configured.
- Check logs for unexpected REST API access or data changes.
- Document compensating controls if vendor guidance is unavailable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-261: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-10275 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
9.8CriticalVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/aliasrobotics/RVD/issues/2565CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Weak Encoding for Password
Weak Encoding for Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.