CVE-2020-10278: RVD#2561: Unprotected BIOS allows user to boot from live OS image.
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.99% (FIRST EPSS); higher than 63% of all records.
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The BIOS onboard MiR's Computer is not protected by password, therefore, it allows a Bad Operator to modify settings such as boot order. This can be leveraged by a Malicious operator to boot from a Live Image.
- Published
- Jun 24, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 63th percentile
- CWE
- CWE-284
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CNA vs NVD score
- NVD
- 4.6
- CNA · Alias
- 6.1
- 1.5 point gap
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| aliasrobotics | mir100 firmware | cpe:2.3:o:aliasrobotics:mir100_firmware |
| aliasrobotics | mir100 | cpe:2.3:h:aliasrobotics:mir100 |
| aliasrobotics | mir200 firmware | cpe:2.3:o:aliasrobotics:mir200_firmware |
| aliasrobotics | mir200 | cpe:2.3:h:aliasrobotics:mir200 |
| aliasrobotics | mir250 firmware | cpe:2.3:o:aliasrobotics:mir250_firmware |
| aliasrobotics | mir250 | cpe:2.3:h:aliasrobotics:mir250 |
| aliasrobotics | mir500 firmware | cpe:2.3:o:aliasrobotics:mir500_firmware |
| aliasrobotics | mir500 | cpe:2.3:h:aliasrobotics:mir500 |
| aliasrobotics | mir1000 firmware | cpe:2.3:o:aliasrobotics:mir1000_firmware |
| aliasrobotics | mir1000 | cpe:2.3:h:aliasrobotics:mir1000 |
| mobile-industrial-robotics | er200 firmware | cpe:2.3:o:mobile-industrial-robotics:er200_firmware |
| mobile-industrial-robotics | er200 | cpe:2.3:h:mobile-industrial-robotics:er200 |
and 8 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Alias). Independent of NVD's CPE analysis and usually ahead of it.
Mobile Industrial Robots A/S MiR100
- v2.8.1.1 and beforeaffected
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- aliasrobotics mir100 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir1000 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir200 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir250 firmwareup to 2.8.1.1 inclusive
- aliasrobotics mir500 firmwareup to 2.8.1.1 inclusive
- enabled-robotics er-flex firmwareup to 2.8.1.1 inclusive
- enabled-robotics er-lite firmwareup to 2.8.1.1 inclusive
- enabled-robotics er-one firmwareup to 2.8.1.1 inclusive
- mobile-industrial-robotics er200 firmwareup to 2.8.1.1 inclusive
- uvd-robots uvd robots firmwareup to 2.8.1.1 inclusive
Same product
aliasrobotics: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-10272RVD#2554: MiR ROS computational graph presents no authentication mechanisms40Plan
- CVE-2020-10271RVD#2555: MiR ROS computational graph is exposed to all network interfaces, including poorly secured wireless networks and open wired ones40Plan
- CVE-2020-10270RVD#2557: Hardcoded Credentials on MiRX00 Control Dashboard40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-10269Jun 24, 2020 · RVD#2566: Hardcoded Credentials on MiRX00 wireless Access Point39Monitor
- ← EarlierCVE-2020-10273Jun 24, 2020 · RVD#2560: Unprotected intellectual property in Mobile Industrial Robots (MiR) controllers30Monitor
- Later →CVE-2020-10279Jun 24, 2020 · RVD#2569: Insecure operating system defaults in MiR robots39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.