<?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>Wed, 07 Oct 2026 10:45:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-54489</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-54489</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The Biosig Project libbiosig&lt;/p&gt;
&lt;p&gt;A stack-based buffer overflow vulnerability exists in the MFER parsing functionality of The Biosig Project libbiosig 3.9.0 and Master Branch (35a819fa). A specially crafted MFER file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability manifests on line 8970 of biosig.c on the current master branch (35a819fa), when the Tag is 63:&#13;
&#13;
                else if (tag==63) {&#13;
                    uint8_t tag2=255, len2=255;&#13;
&#13;
                    count = 0;&#13;
                    while ((count&amp;lt;len) &amp;amp;&amp;amp; !(FlagInfiniteLength &amp;amp;&amp;amp; len2==0 &amp;amp;&amp;amp; tag2==0)){&#13;
                        curPos += ifread(&amp;amp;tag2,1,1,hdr);&#13;
                        curPos += ifread(&amp;amp;len2,1,1,hdr);&#13;
                        if (VERBOSE_LEVEL==9)&#13;
                            fprintf(stdout,&amp;#34;MFER: tag=%3i chan=%2i len=%-4i tag2=%3i len2=%3i curPos=%i %li count=%4i\n&amp;#34;,tag,chan,len,tag2,len2,curPos,iftell(hdr),(int)count);&#13;
&#13;
                        if (FlagInfiniteLength &amp;amp;&amp;amp; len2==0 &amp;amp;&amp;amp; tag2==0) break;&#13;
&#13;
                        count  += (2+len2);&#13;
                        curPos += ifread(&amp;amp;buf,1,len2,hdr);&#13;
&#13;
Here, the number of bytes read is not the Data Length decoded from the current frame in the file (`len`) but rather is a new length contained in a single octet read from the same input file (`len2`). Despite this, a stack-based buffer overflow condition can still occur, as the destination buffer is still `buf`, which has a size of only 128 bytes, wh…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The Biosig Project libbiosig&lt;/p&gt;
&lt;p&gt;A stack-based buffer overflow vulnerability exists in the MFER parsing functionality of The Biosig Project libbiosig 3.9.0 and Master Branch (35a819fa). A specially crafted MFER file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability manifests on line 8970 of biosig.c on the current master branch (35a819fa), when the Tag is 63:&#13;
&#13;
                else if (tag==63) {&#13;
                    uint8_t tag2=255, len2=255;&#13;
&#13;
                    count = 0;&#13;
                    while ((count&amp;lt;len) &amp;amp;&amp;amp; !(FlagInfiniteLength &amp;amp;&amp;amp; len2==0 &amp;amp;&amp;amp; tag2==0)){&#13;
                        curPos += ifread(&amp;amp;tag2,1,1,hdr);&#13;
                        curPos += ifread(&amp;amp;len2,1,1,hdr);&#13;
                        if (VERBOSE_LEVEL==9)&#13;
                            fprintf(stdout,&amp;#34;MFER: tag=%3i chan=%2i len=%-4i tag2=%3i len2=%3i curPos=%i %li count=%4i\n&amp;#34;,tag,chan,len,tag2,len2,curPos,iftell(hdr),(int)count);&#13;
&#13;
                        if (FlagInfiniteLength &amp;amp;&amp;amp; len2==0 &amp;amp;&amp;amp; tag2==0) break;&#13;
&#13;
                        count  += (2+len2);&#13;
                        curPos += ifread(&amp;amp;buf,1,len2,hdr);&#13;
&#13;
Here, the number of bytes read is not the Data Length decoded from the current frame in the file (`len`) but rather is a new length contained in a single octet read from the same input file (`len2`). Despite this, a stack-based buffer overflow condition can still occur, as the destination buffer is still `buf`, which has a size of only 128 bytes, wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-54489</guid>
    </item>
  </channel>
</rss>
