Code execution via unchecked MFER Tag 3 length
Published Dec 11, 2025 · Updated Dec 11, 2025
Stack-based buffer overflow in The BioSig Project libbiosig 3.9.1 allows attackers to execute arbitrary code via a crafted MFER file. In the MFER Tag 3 branch of sopen_extended, ifread copies an attacker-controlled length into the 17-byte stack buffer v after an oversized-length check only prints a warning. Processing a malicious MFER file is sufficient to overwrite adjacent stack data, causing a crash or enabling code execution in the calling process.
Summary
What happened
Stack-based buffer overflow in The BioSig Project libbiosig 3.9.1 allows attackers to execute arbitrary code via a crafted MFER file. In the MFER Tag 3 branch of sopen_extended, ifread copies an attacker-controlled length into the 17-byte stack buffer v after an oversized-length check only prints a warning. Processing a malicious MFER file is sufficient to overwrite adjacent stack data, causing a crash or enabling code execution in the calling process.
The record
- CVE
- CVE-2025-66043
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- The BioSig Project
- Product
- libbiosig
- Classifications
- CWE-121, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Cisco Talos MFER Tag 3 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo