https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 16:31:42 +0000 https://cve.radiocsirt.org/vuln/bdu:2017-02085 bdu:2017-02085 https://cve.radiocsirt.org/vuln/bdu:2017-02085 https://cve.radiocsirt.org/vuln/cleanstart-2024-ax01037 <p><strong>Affected:</strong> CleanStart: ffmpeg4</p> <p>Security vulnerability affects the ffmpeg4 package. In libavformat/nsvdec.</p> <p><strong>Affected:</strong> CleanStart: ffmpeg4</p> <p>Security vulnerability affects the ffmpeg4 package. In libavformat/nsvdec.</p> https://cve.radiocsirt.org/vuln/cleanstart-2024-ax01037 https://cve.radiocsirt.org/vuln/cnvd-2017-30448 cnvd-2017-30448 https://cve.radiocsirt.org/vuln/cnvd-2017-30448 https://cve.radiocsirt.org/vuln/euvd-2026-77976 EUVD-2026-77976 https://cve.radiocsirt.org/vuln/euvd-2026-77976 https://cve.radiocsirt.org/vuln/fkie_cve-2017-14171 <p>In libavformat/nsvdec.c in FFmpeg 2.4 and 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large &#34;table_entries_used&#34; field in the header but does not contain sufficient backing data, is provided, the loop over &#39;table_entries_used&#39; would consume huge CPU resources, since there is no EOF check inside the loop.</p> <p>In libavformat/nsvdec.c in FFmpeg 2.4 and 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large &#34;table_entries_used&#34; field in the header but does not contain sufficient backing data, is provided, the loop over &#39;table_entries_used&#39; would consume huge CPU resources, since there is no EOF check inside the loop.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-14171 https://cve.radiocsirt.org/vuln/ghsa-q3cf-46pw-53qv <p>In libavformat/nsvdec.c in FFmpeg 2.4 and 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large &#34;table_entries_used&#34; field in the header but does not contain sufficient backing data, is provided, the loop over &#39;table_entries_used&#39; would consume huge CPU resources, since there is no EOF check inside the loop.</p> <p>In libavformat/nsvdec.c in FFmpeg 2.4 and 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large &#34;table_entries_used&#34; field in the header but does not contain sufficient backing data, is provided, the loop over &#39;table_entries_used&#39; would consume huge CPU resources, since there is no EOF check inside the loop.</p> https://cve.radiocsirt.org/vuln/ghsa-q3cf-46pw-53qv https://cve.radiocsirt.org/vuln/gsd-2017-14171 gsd-2017-14171 https://cve.radiocsirt.org/vuln/gsd-2017-14171 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-14171 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: ffmpeg</p> <p>In libavformat/nsvdec.c in FFmpeg 2.4 and 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large &#34;table_entries_used&#34; field in the header but does not contain sufficient backing data, is provided, the loop over &#39;table_entries_used&#39; would consume huge CPU resources, since there is no EOF check inside the loop.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: ffmpeg</p> <p>In libavformat/nsvdec.c in FFmpeg 2.4 and 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large &#34;table_entries_used&#34; field in the header but does not contain sufficient backing data, is provided, the loop over &#39;table_entries_used&#39; would consume huge CPU resources, since there is no EOF check inside the loop.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14171