Robot control via predictable REST API tokens
Published Jun 24, 2020 · Updated Sep 16, 2024
Weak REST API token generation in Mobile Industrial Robots A/S MiR100 2.8.1.1 and earlier allows remote attackers to read, write, or delete data. The API derives each token as base64(username:sha256(password)), so unchanged public default web credentials yield a valid authentication key. Access to the robot's Wi-Fi network and unchanged predefined credentials are required; successful use permits robot control, data exfiltration, modification, or deletion.
Summary
What happened
Weak REST API token generation in Mobile Industrial Robots A/S MiR100 2.8.1.1 and earlier allows remote attackers to read, write, or delete data. The API derives each token as base64(username:sha256(password)), so unchanged public default web credentials yield a valid authentication key. Access to the robot's Wi-Fi network and unchanged predefined credentials are required; successful use permits robot control, data exfiltration, modification, or deletion.
The record
- CVE
- CVE-2020-10275
- Published
- Jun 24, 2020
- Updated
- Sep 16, 2024
- Vendor
- Mobile Industrial Robots A/S
- Product
- MiR100
- Classifications
- CWE-326, CWE-261, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v2.8.1.1 and before
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo