Totolink
Totolink A860r Firmware: vulnerabilidades y CVE
Totolink A860r Firmware tiene 8 vulnerabilidades publicadas, 0 de ellas en los últimos 12 meses. 6 son críticas y 0 figuran en el catálogo de explotación activa de CISA.
CVE8
Últimos 12 meses0
Críticas6
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-40475 | Crítica (9.8) | 4.0% | — | 29 sept 2022 | TOTOLINK A860R V4.1.2cu.5182_B20201027 was discovered to contain a command injection via the component /cgi-bin/downloadFile.cgi. |
| CVE-2022-37843 | Crítica (9.8) | 1.7% | — | 6 sept 2022 | In TOTOLINK A860R V4.1.2cu.5182_B20201027 in cstecgi.cgi, the acquired parameters are directly put into the system for execution without filtering, resulting in a command injection vulnerability. |
| CVE-2022-37842 | Crítica (9.8) | 0.93% | — | 6 sept 2022 | In TOTOLINK A860R V4.1.2cu.5182_B20201027, the parameters in infostat.cgi are not filtered, causing a buffer overflow vulnerability. |
| CVE-2022-37841 | Alta (7.5) | 0.70% | — | 6 sept 2022 | In TOTOLINK A860R V4.1.2cu.5182_B20201027 there is a hard coded password for root in /etc/shadow.sample. |
| CVE-2022-37840 | Crítica (9.8) | 0.93% | — | 6 sept 2022 | In TOTOLINK A860R V4.1.2cu.5182_B20201027, the main function in downloadfile.cgi has a buffer overflow vulnerability. |
| CVE-2022-37839 | Crítica (9.8) | 0.93% | — | 6 sept 2022 | TOTOLINK A860R V4.1.2cu.5182_B20201027 is vulnerable to Buffer Overflow via Cstecgi.cgi. |
| CVE-2022-36614 | Alta (7.8) | 0.30% | — | 29 ago 2022 | TOTOLINK A860R V4.1.2cu.5182_B20201027 was discovered to contain a hardcoded password for root at /etc/shadow.sample. |
| CVE-2022-25083 | Crítica (9.8) | 3.1% | — | 24 feb 2022 | TOTOLink A860R V4.1.2cu.5182_B20201027 was discovered to contain a command injection vulnerability in the "Main" function. This vulnerability allows attackers to execute arbitrary commands via the QUERY_STRING parameter. |