https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 06:27:53 +0000 https://cve.radiocsirt.org/vuln/bdu:2017-02089 bdu:2017-02089 https://cve.radiocsirt.org/vuln/bdu:2017-02089 https://cve.radiocsirt.org/vuln/cleanstart-2024-ct58495 <p><strong>Affected:</strong> CleanStart: ffmpeg4</p> <p>Security vulnerability affects the ffmpeg4 package. In FFmpeg 3.</p> <p><strong>Affected:</strong> CleanStart: ffmpeg4</p> <p>Security vulnerability affects the ffmpeg4 package. In FFmpeg 3.</p> https://cve.radiocsirt.org/vuln/cleanstart-2024-ct58495 https://cve.radiocsirt.org/vuln/cnvd-2017-30431 cnvd-2017-30431 https://cve.radiocsirt.org/vuln/cnvd-2017-30431 https://cve.radiocsirt.org/vuln/euvd-2026-77769 EUVD-2026-77769 https://cve.radiocsirt.org/vuln/euvd-2026-77769 https://cve.radiocsirt.org/vuln/fkie_cve-2017-14059 <p>In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large &#34;duration&#34; field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.</p> <p>In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large &#34;duration&#34; field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-14059 https://cve.radiocsirt.org/vuln/ghsa-crp8-6v6m-qvrp <p>In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large &#34;duration&#34; field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.</p> <p>In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large &#34;duration&#34; field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.</p> https://cve.radiocsirt.org/vuln/ghsa-crp8-6v6m-qvrp https://cve.radiocsirt.org/vuln/gsd-2017-14059 gsd-2017-14059 https://cve.radiocsirt.org/vuln/gsd-2017-14059 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-14059 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: ffmpeg</p> <p>In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large &#34;duration&#34; field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: ffmpeg</p> <p>In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large &#34;duration&#34; field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14059