Skip to main content
VulnerabilityPublished Updated

CVE-2024-23313: The Biosig Project libbiosig · Integer Underflow

Affects The Biosig Project libbiosigSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 78% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
The Biosig Project libbiosigAffected
  • =2.5.0
Fixed in–

AI-suggested

  1. Monitor official Biosig Project channels for patches or updates addressing CVE-2024-23313 and apply them promptly once available.
  2. Until patches are released, restrict the acceptance and processing of .famos files to trusted sources only, implementing strict validation and sanitization of input files.
  3. Employ application-level sandboxing or containerization to isolate libbiosig usage and limit the impact of potential exploitation.
  4. Use runtime memory protection technologies such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and Control Flow Integrity (CFI) to mitigate exploitation attempts.
  5. Conduct thorough code audits and fuzz testing on the sopen_FAMOS_read functionality if custom or extended versions of libbiosig are in use.
  6. Implement network-level controls to detect and block suspicious file transfers involving .famos files, including email filtering and intrusion detection systems tuned for anomalous biosignal file activity.
  7. Educate relevant staff on the risks of opening untrusted biosignal files and enforce strict operational security policies around data handling in biomedical environments.

Description

An integer underflow 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

Community reviews

Loading reviews…