https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:17:11 +0000 https://cve.radiocsirt.org/vuln/bdu:2017-02091 bdu:2017-02091 https://cve.radiocsirt.org/vuln/bdu:2017-02091 https://cve.radiocsirt.org/vuln/cleanstart-2024-mi06720 <p><strong>Affected:</strong> CleanStart: ffmpeg4</p> <p>Security vulnerability affects the ffmpeg4 package. In libavformat/rl2.</p> <p><strong>Affected:</strong> CleanStart: ffmpeg4</p> <p>Security vulnerability affects the ffmpeg4 package. In libavformat/rl2.</p> https://cve.radiocsirt.org/vuln/cleanstart-2024-mi06720 https://cve.radiocsirt.org/vuln/cnvd-2017-30440 cnvd-2017-30440 https://cve.radiocsirt.org/vuln/cnvd-2017-30440 https://cve.radiocsirt.org/vuln/euvd-2026-77798 EUVD-2026-77798 https://cve.radiocsirt.org/vuln/euvd-2026-77798 https://cve.radiocsirt.org/vuln/fkie_cve-2017-14056 <p>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 &#34;frame_count&#34; 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.</p> <p>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 &#34;frame_count&#34; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-14056 https://cve.radiocsirt.org/vuln/ghsa-r5h2-24x5-fv2h <p>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 &#34;frame_count&#34; 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.</p> <p>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 &#34;frame_count&#34; 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.</p> https://cve.radiocsirt.org/vuln/ghsa-r5h2-24x5-fv2h https://cve.radiocsirt.org/vuln/gsd-2017-14056 gsd-2017-14056 https://cve.radiocsirt.org/vuln/gsd-2017-14056 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10754-1 <p>ffmpeg-4-4.4-5.2 on GA media</p> <p>ffmpeg-4-4.4-5.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10754-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14056 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: ffmpeg</p> <p>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 &#34;frame_count&#34; 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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: ffmpeg</p> <p>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 &#34;frame_count&#34; 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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14056