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

Summaryinfo

A vulnerability has been found in Biosig libbiosig 3.9.0 and classified as critical. The impacted element is an unknown function of the file biosig.c of the component MFER Parser. The manipulation leads to stack-based overflow. This vulnerability is uniquely identified as CVE-2025-54492. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Biosig libbiosig 3.9.0. It has been rated as critical. This issue affects an unknown part of the file biosig.c of the component MFER Parser. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to 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). Impacted is 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 9141 of biosig.c on the current master branch (35a819fa), when the Tag is 67: else if (tag==67) //0x43: Sample skew { int skew=0; // [1] curPos += ifread(&skew, 1, len,hdr); In this case, the address of the newly-defined integer `skew` \[1\] is overflowed instead of `buf`. This means a stack overflow can occur using much smaller values of `len` in this code path.

The advisory is shared at talosintelligence.com. The identification of this vulnerability is CVE-2025-54492 since 07/23/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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/03/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-25671). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion