Crestron
Crestron Dm-txrx-100-str Firmware: vulnerabilidades y CVE
Crestron Dm-txrx-100-str Firmware tiene 6 vulnerabilidades publicadas, 0 de ellas en los últimos 12 meses. 5 son críticas y 0 figuran en el catálogo de explotación activa de CISA.
CVE6
Últimos 12 meses0
Críticas5
Explotadas activamente0
Todas las vulnerabilidades en el catálogo →⭐ Seguir esta tecnología
Últimas vulnerabilidades
| CVE | Severidad | EPSS | Explotación activa | Publicada | Descripción |
|---|---|---|---|---|---|
| CVE-2016-5671 | Alta (8.8) | 0.86% | — | 3 ago 2016 | Multiple cross-site request forgery (CSRF) vulnerabilities on Crestron Electronics DM-TXRX-100-STR devices with firmware through 1.3039.00040 allow remote attackers to hijack the authentication of arbitrary users. |
| CVE-2016-5670 | Crítica (9.8) | 3.2% | — | 3 ago 2016 | Crestron Electronics DM-TXRX-100-STR devices with firmware before 1.3039.00040 have a hardcoded password of admin for the admin account, which makes it easier for remote attackers to obtain access via the web management… |
| CVE-2016-5669 | Crítica (9.8) | 1.6% | — | 3 ago 2016 | Crestron Electronics DM-TXRX-100-STR devices with firmware before 1.3039.00040 use a hardcoded 0xb9eed4d955a59eb3 X.509 certificate from an OpenSSL Test Certification Authority, which makes it easier for remote… |
| CVE-2016-5668 | Crítica (9.8) | 4.4% | — | 3 ago 2016 | Crestron Electronics DM-TXRX-100-STR devices with firmware before 1.3039.00040 allow remote attackers to bypass authentication and change settings via a JSON API call. |
| CVE-2016-5667 | Crítica (9.8) | 4.4% | — | 3 ago 2016 | Crestron Electronics DM-TXRX-100-STR devices with firmware before 1.3039.00040 allow remote attackers to bypass authentication via a direct request to a page other than index.html. |
| CVE-2016-5666 | Crítica (9.8) | 4.2% | — | 3 ago 2016 | Crestron Electronics DM-TXRX-100-STR devices with firmware before 1.3039.00040 rely on the client to perform authentication, which allows remote attackers to obtain access by setting the value of objresp.authenabled to… |