<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 10:18:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2017-02090</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2017-02090</link>
      <description>bdu:2017-02090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2017-02090</guid>
    </item>
    <item>
      <title>CLEANSTART-2024-EC09476 — In FFmpeg 3</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2024-ec09476</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: ffmpeg4&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the ffmpeg4 package. In FFmpeg 3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: ffmpeg4&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the ffmpeg4 package. In FFmpeg 3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2024-ec09476</guid>
    </item>
    <item>
      <title>cnvd-2017-30442</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-30442</link>
      <description>cnvd-2017-30442</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-30442</guid>
    </item>
    <item>
      <title>EUVD-2026-77818</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-77818</link>
      <description>EUVD-2026-77818</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-77818</guid>
    </item>
    <item>
      <title>fkie_cve-2017-14057</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-14057</link>
      <description>&lt;p&gt;In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large &amp;#34;name_len&amp;#34; or &amp;#34;count&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large &amp;#34;name_len&amp;#34; or &amp;#34;count&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-14057</guid>
    </item>
    <item>
      <title>GHSA-vwrx-gcwc-3w8c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vwrx-gcwc-3w8c</link>
      <description>&lt;p&gt;In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large &amp;#34;name_len&amp;#34; or &amp;#34;count&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large &amp;#34;name_len&amp;#34; or &amp;#34;count&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vwrx-gcwc-3w8c</guid>
    </item>
    <item>
      <title>gsd-2017-14057</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-14057</link>
      <description>gsd-2017-14057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-14057</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:10754-1 — ffmpeg-4-4.4-5.2 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:10754-1</link>
      <description>&lt;p&gt;ffmpeg-4-4.4-5.2 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ffmpeg-4-4.4-5.2 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:10754-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2017-14057</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14057</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ffmpeg&lt;/p&gt;
&lt;p&gt;In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large &amp;#34;name_len&amp;#34; or &amp;#34;count&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ffmpeg&lt;/p&gt;
&lt;p&gt;In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large &amp;#34;name_len&amp;#34; or &amp;#34;count&amp;#34; field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14057</guid>
    </item>
  </channel>
</rss>
