Skip to main content
CVE-2024-22097VulnerabilityPublished Updated

CVE-2024-22097: The Biosig Project libbiosig · Double Free

Affects The Biosig Project libbiosigSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

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

What to do

Affected software

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

AI-suggested

To mitigate CVE-2024-22097, European organizations should: 1) Monitor The Biosig Project's official channels for patches or updates addressing this vulnerability and apply them promptly once available. 2) Implement strict validation and sanitization of all .vdhr files before processing, including rejecting files from untrusted or unauthenticated sources. 3) Employ application-level sandboxing or containerization to isolate the libbiosig processing environment, limiting the impact of potential exploitation. 4) Restrict network access to systems that process biosignal data to trusted users and devices only, reducing exposure to malicious files. 5) Conduct code audits or use static analysis tools on custom applications integrating libbiosig to identify and remediate unsafe file handling practices. 6) Maintain up-to-date endpoint protection and intrusion detection systems capable of identifying anomalous behavior indicative of exploitation attempts. 7) Educate staff in biomedical and research departments about the risks of processing untrusted biosignal files and enforce policies for secure data handling. These targeted measures go beyond generic advice by focusing on the specific file type and processing context relevant to this vulnerability.

Description

A double-free vulnerability exists in the BrainVision Header Parsing functionality of The Biosig Project libbiosig Master Branch (ab0ee111) and 2.5.0. A specially crafted .vdhr file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.

References

Community reviews

Loading reviews…