Vulnerabilidades

Resumen — últimos 7 días

Vulnerabilidades nuevas3007▼ 68 respecto a la semana anterior
Críticas / altas1421▲ 55 respecto a la semana anterior
Nueva explotación activa (KEV)4▼ 5 respecto a la semana anterior
Sin puntuar (sin CVSS)382▼ 128 respecto a la semana anterior
–

7 resultados, ordenados por fecha de publicación (más recientes primero)

CVEEstadoSeveridadEPSS Explotación activaTecnologías afectadasPublicada ▼Modificada Descripción
ModificadaCrítica (9.8)0.97%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
MiR robot controllers (central computation unit) makes use of Ubuntu 16.04.2 an operating system, Thought for desktop uses, this operating system presents insecure defaults for robots. These insecurities include a way for users to escalate their access beyond what they were granted via file creation, access race…
ModificadaMedia (4.6)0.97%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
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.
ModificadaAlta (7.5)0.86%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
MiR controllers across firmware versions 2.8.1.1 and before do not encrypt or protect in any way the intellectual property artifacts installed in the robots. This flaw allows attackers with access to the robot or the robot network (while in combination with other flaws) to retrieve and easily exfiltrate all installed…
ModificadaCrítica (9.8)2.5%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computational graph without any sort of authentication. This allows attackers with access to the internal wireless and wired networks to take control of the robot seamlessly. In combination with CVE-2020-10269 and…
ModificadaCrítica (9.8)1.8%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
MiR100, MiR200 and other MiR robots use the Robot Operating System (ROS) default packages exposing the computational graph to all network interfaces, wireless and wired. This is the result of a bad set up and can be mitigated by appropriately configuring ROS and/or applying custom patches as appropriate. Currently,…
ModificadaCrítica (9.8)1.7%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
Out of the wired and wireless interfaces within MiR100, MiR200 and other vehicles from the MiR fleet, it's possible to access the Control Dashboard on a hardcoded IP address. Credentials to such wireless interface default to well known and widely spread users (omitted) and passwords (omitted). This information is also…
ModificadaCrítica (9.8)1.4%—Aliasrobotics Mir100 FirmwareAliasrobotics Mir200 FirmwareAliasrobotics Mir250 FirmwareAliasrobotics Mir500 Firmware+624/6/202017/6/2026
One of the wireless interfaces within MiR100, MiR200 and possibly (according to the vendor) other MiR fleet vehicles comes pre-configured in WiFi Master (Access Point) mode. Credentials to such wireless Access Point default to well known and widely spread SSID (MiR_RXXXX) and passwords (omitted). This information is…