Vulnerabilidades
Resumen — últimos 7 días
Vulnerabilidades nuevas2862▼ 326 respecto a la semana anterior
Críticas / altas1389▼ 28 respecto a la semana anterior
Nueva explotación activa (KEV)4▼ 5 respecto a la semana anterior
Sin puntuar (sin CVSS)293▼ 216 respecto a la semana anterior
5 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.8) | 0.87% | — | Gif2apng Project Gif2apngDebian Linux | 28/12/2021 | 17/6/2026 | An issue was discovered in gif2apng 1.9. There is a heap-based buffer overflow in the main function. It allows an attacker to write 2 bytes outside the boundaries of the buffer. | |
| Modificada | Alta (7.8) | 0.87% | — | Gif2apng Project Gif2apngDebian Linux | 28/12/2021 | 17/6/2026 | An issue was discovered in gif2apng 1.9. There is a heap-based buffer overflow within the main function. It allows an attacker to write data outside of the allocated buffer. The attacker has control over a part of the address that data is written to, control over the written data, and (to some extent) control over the… | |
| Modificada | Alta (7.8) | 0.87% | — | Gif2apng Project Gif2apngDebian Linux | 28/12/2021 | 17/6/2026 | An issue was discovered in gif2apng 1.9. There is a heap-based buffer overflow vulnerability in the DecodeLZW function. It allows an attacker to write a large amount of arbitrary data outside the boundaries of a buffer. | |
| Modificada | Alta (7.8) | 0.73% | — | Gif2apng Project Gif2apng | 28/12/2021 | 17/6/2026 | An issue was discovered in gif2apng 1.9. There is a stack-based buffer overflow involving a while loop. An attacker has little influence over the data written to the stack, making it unlikely that the flow of control can be subverted. | |
| Modificada | Alta (7.8) | 0.73% | — | Gif2apng Project Gif2apng | 28/12/2021 | 17/6/2026 | An issue was discovered in gif2apng 1.9. There is a stack-based buffer overflow involving a for loop. An attacker has little influence over the data written to the stack, making it unlikely that the flow of control can be subverted. |