Vulnerabilidades
Resumen — últimos 7 días
Vulnerabilidades nuevas2570▼ 302 respecto a la semana anterior
Críticas / altas1352▲ 100 respecto a la semana anterior
Nueva explotación activa (KEV)5▼ 7 respecto a la semana anterior
Sin puntuar (sin CVSS)56▼ 472 respecto a la semana anterior
6 resultados, ordenados por fecha de publicación (más recientes primero)
| CVE | Estado | Severidad | EPSS | Explotación activa | Tecnologías afectadas | Publicada ▼ | Modificada | Descripción |
|---|---|---|---|---|---|---|---|---|
| Modificada | Alta (7.5) | 1.1% | — | Freetakserver-ui Project Freetakserver-ui | 11/3/2022 | 17/6/2026 | FreeTAKServer-UI v1.9.8 was discovered to leak sensitive API and Websocket keys. | |
| Modificada | Media (6.5) | 0.74% | — | Freetakserver-ui Project Freetakserver-ui | 11/3/2022 | 17/6/2026 | An issue in the ?filename= argument of the route /DataPackageTable in FreeTAKServer-UI v1.9.8 allows attackers to place arbitrary files anywhere on the system. | |
| Modificada | Alta (8.8) | 1.1% | — | Freetakserver-ui Project Freetakserver-ui | 11/3/2022 | 17/6/2026 | FreeTAKServer 1.9.8 contains a hardcoded Flask secret key which allows attackers to create crafted cookies to bypass authentication or escalate privileges. | |
| Modificada | Alta (7.5) | 1.0% | — | Freetakserver-ui Project Freetakserver-ui | 11/3/2022 | 17/6/2026 | An access control issue in the component /ManageRoute/postRoute of FreeTAKServer v1.9.8 allows unauthenticated attackers to cause a Denial of Service (DoS) via an unusually large amount of created routes, or create unsafe or false routes for legitimate users. | |
| Modificada | Media (5.4) | 0.49% | — | Freetakserver-ui Project Freetakserver-ui | 11/3/2022 | 17/6/2026 | FreeTAKServer-UI v1.9.8 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the Callsign parameter. | |
| Modificada | Media (6.5) | 0.88% | — | Freetakserver-ui Project Freetakserver-ui | 11/3/2022 | 17/6/2026 | FreeTAKServer-UI v1.9.8 was discovered to contain a SQL injection vulnerability via the API endpoint /AuthenticateUser. |