CVE-2024-23606: The Biosig Project libbiosig · Incorrect Calculation of Buffer Size
Affects The Biosig Project libbiosigSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:15 UTC
- EPSS
- 1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| The Biosig Project libbiosig | Affected
| Fixed in– |
AI-suggested
1. Monitor The Biosig Project repositories and official channels for patches addressing CVE-2024-23606 and apply them immediately upon release. 2. Until patches are available, implement strict input validation and sanitization for .famos files to detect and block malformed or suspicious files. 3. Employ sandboxing or containerization techniques to isolate processes handling biosignal files, limiting the impact of potential exploitation. 4. Restrict access to systems processing .famos files to trusted users and networks, minimizing exposure to untrusted file sources. 5. Conduct code audits and security reviews of any custom software integrating libbiosig to identify and remediate unsafe file handling practices. 6. Deploy network-level protections such as file scanning and intrusion detection systems tuned to detect anomalous activity related to biosignal file processing. 7. Educate staff in biomedical and IT departments about the risks of opening untrusted biosignal files and enforce policies for secure file handling. 8. Maintain up-to-date backups of critical data and systems to enable recovery in case of compromise. These targeted measures go beyond generic advice by focusing on the specific file format, processing context, and operational environment of libbiosig deployments.
Description
An out-of-bounds write vulnerability exists in the sopen_FAMOS_read functionality of The Biosig Project libbiosig 2.5.0 and Master Branch (ab0ee111). A specially crafted .famos file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.
References
- talosintelligence.com/vulnerability_reports/TALOS-2024-1925 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OIRLGNQM33KAWVWP5RPMAPHWNP3IY5YW/ (opens in a new tab)
- talosintelligence.com/vulnerability_reports/TALOS-2024-1925 (opens in a new tab)