Secheron
Secheron Sepcos Control AND Protection Relay Firmware: vulnerabilidades y CVE
Secheron Sepcos Control AND Protection Relay Firmware tiene 7 vulnerabilidades publicadas, 0 de ellas en los últimos 12 meses. 4 son críticas y 0 figuran en el catálogo de explotación activa de CISA.
CVE7
Últimos 12 meses0
Críticas4
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-2022-2105 | Crítica (9.1) | 1.1% | — | 24 jun 2022 | Client-side JavaScript controls may be bypassed to change user credentials and permissions without authentication, including a “root” user level meant only for the vendor. Web server root level access allows for… |
| CVE-2022-2104 | Crítica (9.8) | 1.1% | — | 24 jun 2022 | The www-data (Apache web server) account is configured to run sudo with no password for many commands (including /bin/sh and /bin/bash). |
| CVE-2022-2103 | Crítica (9.1) | 1.0% | — | 24 jun 2022 | An attacker with weak credentials could access the TCP port via an open FTP port, allowing an attacker to read sensitive files and write to remotely executable directories. |
| CVE-2022-2102 | Alta (7.5) | 0.92% | — | 24 jun 2022 | Controls limiting uploads to certain file extensions may be bypassed. This could allow an attacker to intercept the initial file upload page response and modify the associated code. This modified code can be forwarded… |
| CVE-2022-1668 | Crítica (9.8) | 2.2% | — | 24 jun 2022 | Weak default root user credentials allow remote attackers to easily obtain OS superuser privileges over the open TCP port for SSH. |
| CVE-2022-1667 | Alta (7.5) | 1.3% | — | 24 jun 2022 | Client-side JavaScript controls may be bypassed by directly running a JS function to reboot the PLC (e.g., from the browser console) or by loading the corresponding, browser accessible PHP script |
| CVE-2022-1666 | Media (6.5) | 0.79% | — | 24 jun 2022 | The default password for the web application’s root user (the vendor’s private account) was weak and the MD5 hash was used to crack the password using a widely available open-source tool. |