Security readout for executives and security teams
Plain-English summary
This issue exposes third-party URCap software intellectual property on Universal Robots CB 3.1 controllers. Installed URCaps are stored as unprotected zip files, so someone with robot or robot-network access, possibly aided by other flaws, could copy proprietary logic. The main business risk is confidentiality loss, not robot takeover.
Executive priority
Prioritize sites where proprietary URCaps encode process know-how, custom automation logic, or partner software. This is a high confidentiality issue; urgency depends on who can access controller networks and whether valuable URCaps are deployed.
Technical view
CVE-2020-10267 is a CWE-311 cleartext storage issue in Universal Robots CB 3.1 controllers affecting UR3, UR5, and UR10 deployments. Tested firmware versions include 1.10, 1.11, 1.12, and 1.12.1. URCaps are stored unencrypted under /root/.urcaps, enabling retrieval of installed UR+ artifacts when access exists.
Likely exposure
Exposure is most likely where UR3, UR5, or UR10 robots use CB 3.1 controllers with installed URCaps and are reachable by users, vendors, maintenance systems, or networks beyond tightly controlled robot cells.
Exploitation context
The source bundle does not show active exploitation or CISA KEV listing. The stated scenario requires access to the robot or robot network, and may require combination with other flaws. Impact is high confidentiality loss of installed URCap intellectual property.
Researcher notes
Evidence supports unprotected storage of URCap artifacts, not integrity or availability compromise. The affected-version statement is broad, with specific tested firmware named. No patch, workaround, or active exploitation evidence is included in the provided sources.
Mitigation direction
- Check Universal Robots guidance for fixed firmware or supported protections.
- Limit controller network reachability to required engineering and operations systems.
- Treat URCap packages and backups as sensitive intellectual property.
- Remove unused URCaps from production controllers after validation.
- Restrict physical and administrative access to robot controllers.
- Review vendor support agreements before altering controller software.
Validation and detection
- Inventory UR3, UR5, and UR10 deployments using CB 3.1 controllers.
- Record controller firmware versions and installed URCaps.
- Using authorized access, verify whether URCaps are present in controller storage.
- Review who can reach the robot network and controller interfaces.
- Check backups or maintenance exports for exposed URCap artifacts.
- Document compensating controls where no vendor fix is confirmed.
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-311: 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 lookupCVE-2020-10267 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
- High
- CVSS
- 7.5 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.5HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/aliasrobotics/RVD/issues/1489CVE 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.
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.