<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 20:22:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2017-14171</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2017-14171</link>
      <description>&lt;p&gt;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 &amp;#34;table_entries_used&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loop over &amp;#39;table_entries_used&amp;#39; would consume huge CPU resources, since there is no EOF check inside the loop.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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 &amp;#34;table_entries_used&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loop over &amp;#39;table_entries_used&amp;#39; would consume huge CPU resources, since there is no EOF check inside the loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2017-14171</guid>
    </item>
  </channel>
</rss>
