Skip to main content
CVE-2024-21795VulnerabilityPublished Updated

CVE-2024-21795: The Biosig Project libbiosig · Heap-based Buffer Overflow

Affects The Biosig Project libbiosigSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 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 2026-10-25.

What to do

Affected software

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

AI-suggested

1. Monitor The Biosig Project’s official channels for patches addressing CVE-2024-21795 and apply updates immediately upon release. 2. Until patches are available, implement strict input validation and sanitization for all .egi files processed by libbiosig to detect and block malformed or suspicious files. 3. Employ sandboxing or containerization techniques to isolate the libbiosig parsing process, limiting the impact of potential exploitation. 4. Restrict access to systems processing .egi files to trusted users and networks, minimizing exposure to untrusted file sources. 5. Conduct code audits and static analysis on any custom integrations using libbiosig to identify and remediate unsafe parsing practices. 6. Enhance monitoring and logging for abnormal application behavior or crashes related to .egi file processing to detect exploitation attempts early. 7. Educate staff handling biomedical data about the risks of opening untrusted .egi files and enforce policies against using files from unknown sources. 8. Consider deploying application-layer firewalls or intrusion prevention systems capable of inspecting and filtering malicious file content targeting libbiosig.

Description

A heap-based buffer overflow vulnerability exists in the .egi parsing functionality of The Biosig Project libbiosig 2.5.0 and Master Branch (ab0ee111). A specially crafted .egi file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.

References

Community reviews

Loading reviews…