Robot takeover via unsigned component installation
Published Apr 6, 2020 · Updated Sep 16, 2024
Missing integrity checks in URx for CB3 SW 3.3 through 3.12.1 allow remote attackers to take control via a malicious URCap. The controller's UR+ installation path accepts a downloaded .urcap component without verifying its integrity or a digital signature, so a substituted package is trusted and installed. Exploitation requires an adversary-in-the-middle position and a user to install the substituted component; the installed code grants complete control of the robot.
Summary
What happened
Missing integrity checks in URx for CB3 SW 3.3 through 3.12.1 allow remote attackers to take control via a malicious URCap. The controller's UR+ installation path accepts a downloaded .urcap component without verifying its integrity or a digital signature, so a substituted package is trusted and installed. Exploitation requires an adversary-in-the-middle position and a user to install the substituted component; the installed code grants complete control of the robot.
The record
- CVE
- CVE-2020-10266
- Published
- Apr 6, 2020
- Updated
- Sep 16, 2024
- Vendor
- SINTEF Manufacturing
- Product
- URx
- Classifications
- CWE-345, CWE-353, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 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=CB3 SW Versions 3.3 up to 3.12.1
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