Описание
In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted RL2 file, which claims a large "frame_count" field in the header but does not contain sufficient backing data, is provided, the loops (for offset and size tables) would consume huge CPU and memory resources, since there is no EOF check inside these loops.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | ignored | end of life |
| bionic | not-affected | 7:3.3.4-1 |
| devel | not-affected | 7:3.3.4-1 |
| esm-apps/bionic | not-affected | 7:3.3.4-1 |
| esm-apps/xenial | released | 7:2.8.14-0ubuntu0.16.04.1 |
| esm-infra-legacy/trusty | DNE | |
| precise/esm | DNE | |
| trusty | DNE | |
| trusty/esm | DNE | |
| upstream | needs-triage |
Показывать по
Ссылки на источники
7.1 High
CVSS2
6.5 Medium
CVSS3
Связанные уязвимости
In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted RL2 file, which claims a large "frame_count" field in the header but does not contain sufficient backing data, is provided, the loops (for offset and size tables) would consume huge CPU and memory resources, since there is no EOF check inside these loops.
In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due t ...
In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted RL2 file, which claims a large "frame_count" field in the header but does not contain sufficient backing data, is provided, the loops (for offset and size tables) would consume huge CPU and memory resources, since there is no EOF check inside these loops.
Уязвимость функции rl2_read_header мультимедийной библиотеки Ffmpeg (libavformat/rl2.c), позволяющая нарушителю вызвать расходование памяти и отказ в обслуживании
7.1 High
CVSS2
6.5 Medium
CVSS3