Количество 7
Количество 7
GHSA-h246-95j7-6pm6
In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.
CVE-2017-14222
In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.
CVE-2017-14222
In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.
CVE-2017-14222
In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack ...
BDU:2017-02298
Уязвимость функции read_tfra() мультимедийной библиотеки FFmpeg (libavformat/mov.c), позволяющая нарушителю вызвать отказ в обслуживании
openSUSE-SU-2017:2501-1
Security update for ffmpeg, ffmpeg2
openSUSE-SU-2017:2502-1
Security update for ffmpeg, ffmpeg2
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
| GHSA-h246-95j7-6pm6 In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop. | CVSS3: 6.5 | 2% Низкий | больше 4 лет назад |
 | CVE-2017-14222 In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop. | CVSS3: 6.5 | 2% Низкий | около 9 лет назад |
 | CVE-2017-14222 In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MOV file, which claims a large "item_count" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU and memory resources, since there is no EOF check inside the loop. | CVSS3: 6.5 | 2% Низкий | около 9 лет назад |
| CVE-2017-14222 In libavformat/mov.c in FFmpeg 3.3.3, a DoS in read_tfra() due to lack ... | CVSS3: 6.5 | 2% Низкий | около 9 лет назад |
 | BDU:2017-02298 Уязвимость функции read_tfra() мультимедийной библиотеки FFmpeg (libavformat/mov.c), позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 6.5 | 2% Низкий | около 9 лет назад |
 | openSUSE-SU-2017:2501-1 Security update for ffmpeg, ffmpeg2 | почти 9 лет назад | ||
| openSUSE-SU-2017:2502-1 Security update for ffmpeg, ffmpeg2 | почти 9 лет назад |
Уязвимостей на страницу