Biosig libbiosig 3.9.0 MFER Parser biosig.c stack-based overflow

Summaryinfo

A vulnerability classified as critical has been found in Biosig libbiosig 3.9.0. This vulnerability affects unknown code of the file biosig.c of the component MFER Parser. This manipulation causes stack-based overflow. This vulnerability appears as CVE-2025-54488. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Biosig libbiosig 3.9.0 and classified as critical. Affected by this vulnerability is some unknown processing of the file biosig.c of the component MFER Parser. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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 8850 of biosig.c on the current master branch (35a819fa), when the Tag is 13: else if (tag==13) { if (len>8) fprintf(stderr,"Warning MFER tag13 incorrect length %i>8\n",len); curPos += ifread(&buf,1,len,hdr);

The advisory is shared at talosintelligence.com. This vulnerability is known as CVE-2025-54488 since 07/23/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/02/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-25675). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Biosig

Name

• libbiosig

Version

• 3.9.0

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion