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

Summaryinfo

A vulnerability classified as critical was found in Biosig libbiosig 3.9.0. Affected by this issue is some unknown functionality of the file biosig.c of the component MFER Parser. The manipulation results in stack-based overflow. This vulnerability is known as CVE-2025-54482. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in Biosig libbiosig 3.9.0. Affected is an unknown function of the file biosig.c of the component MFER Parser. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as 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). This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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

The advisory is shared for download at talosintelligence.com. This vulnerability is traded as CVE-2025-54482 since 07/23/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (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.

Once again VulDB remains the best source for 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

Once again VulDB remains the best source for vulnerability data.

Discussion