CVE-2024-21812: The Biosig Project libbiosig · Integer Overflow or Wraparound
Affects The Biosig Project libbiosigSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.7% chance of exploitation in 30 days – higher than 77% 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’s official channels for patches addressing CVE-2024-21812 and apply them immediately upon release. 2. Until patches are available, restrict processing of .famos files to trusted and verified sources only, implementing strict input validation and file integrity checks. 3. Employ runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and stack canaries to reduce exploitation success. 4. Use application sandboxing or containerization to isolate processes handling .famos files, limiting potential damage from exploitation. 5. Conduct code audits and static analysis on any custom integrations with libbiosig to identify and remediate unsafe handling of biosignal files. 6. Implement network-level controls to monitor and block suspicious traffic targeting services that process .famos files. 7. Educate relevant staff about the risks of opening untrusted biosignal files and enforce strict operational procedures for file handling. 8. Prepare incident response plans specifically addressing potential exploitation scenarios involving libbiosig vulnerabilities.
Description
An integer overflow 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 an out-of-bounds write which in turn can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.
References
- talosintelligence.com/vulnerability_reports/TALOS-2024-1921 (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-1921 (opens in a new tab)