Code execution via unchecked MFER tag length
Published Aug 25, 2025 · Updated Nov 3, 2025
Stack-based buffer overflow in libbiosig 3.9.0 and Master Branch (35a819fa) allows attackers to execute code via a crafted MFER file. The MFER tag-6 handler in biosig.c warns when the declared length exceeds four bytes but still passes that untrusted length to ifread for a fixed stack buffer. The vulnerable library must parse the malicious file; successful exploitation executes code in the context of the consuming process.
Summary
What happened
Stack-based buffer overflow in libbiosig 3.9.0 and Master Branch (35a819fa) allows attackers to execute code via a crafted MFER file. The MFER tag-6 handler in biosig.c warns when the declared length exceeds four bytes but still passes that untrusted length to ifread for a fixed stack buffer. The vulnerable library must parse the malicious file; successful exploitation executes code in the context of the consuming process.
The record
- CVE
- CVE-2025-54484
- Published
- Aug 25, 2025
- Updated
- Nov 3, 2025
- Vendor
- The BioSig Project
- Product
- libbiosig
- Classifications
- CWE-121, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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.0
- Affected versionversion=Master Branch (35a819fa)
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-6 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