CVE-2020-10274

HighCVSS 7.1/10Last modified Jun 17, 2026

Description

The access tokens for the REST API are directly derived (sha256 and base64 encoding) from the publicly available default credentials from the Control Dashboard (refer to CVE-2020-10270 for related flaws). This flaw in combination with CVE-2020-10273 allows any attacker connected to the robot networks (wired or wireless) to exfiltrate all stored data (e.g. indoor mapping images) and associated metadata from the robot's database.

Metrics

CVSS 3.1 7.1/10CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Weakness enumeration

Affected software

No affected versions have been published.

Timeline

Published
Jun 24, 2020
Last modified
Jun 17, 2026
NVD status
Modified

Related CVEs from 2020

CVE-2020-102759.8The access tokens for the REST API are directly derived from the publicly available default credentials for the web interface. Given a USERNCVE-2020-102769.8The password for the safety PLC is the default and thus easy to find (in manuals, etc.). This allows a manipulated program to be uploaded toCVE-2020-102776.4There is no mechanism in place to prevent a bad operator to boot from a live OS image, this can lead to extraction of sensible files (such aCVE-2020-102784.6The BIOS onboard MiR's Computer is not protected by password, therefore, it allows a Bad Operator to modify settings such as boot order. ThiCVE-2020-102799.8MiR robot controllers (central computation unit) makes use of Ubuntu 16.04.2 an operating system, Thought for desktop uses, this operating sCVE-2020-10287.8A memory corruption vulnerability exists when Windows Media Foundation improperly handles objects in memory. An attacker who successfully exCVE-2020-102807.5The Apache server on port 80 that host the web interface is vulnerable to a DoS by spamming incomplete HTTP headers, effectively blocking thCVE-2020-102817.5This vulnerability applies to the Micro Air Vehicle Link (MAVLink) protocol and allows a remote attacker to gain access to sensitive informaCVE-2020-102829.8The Micro Air Vehicle Link (MAVLink) protocol presents no authentication mechanism on its version 1.0 (nor authorization) whichs leads to a CVE-2020-102839.8The Micro Air Vehicle Link (MAVLink) protocol presents authentication mechanisms on its version 2.0 however according to its documentation, CVE-2020-102849.1No authentication is required to control the robot inside the network, moreso the latest available user manual shows an option that lets theCVE-2020-102859.8The authentication implementation on the xArm controller has very low entropy, making it vulnerable to a brute-force attack. There is no mec
CVE-2020-10274: High severity, CVSS 7.1 | Vulnix