Skip to main content
CVE-2024-23809VulnerabilityPublished Updated

CVE-2024-23809: 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 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: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
Debiandebian/libbiosigpkg:deb/debian/libbiosigOther threatsAffected
  • =2.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor The Biosig Project's official channels for patches addressing CVE-2024-23809 and apply updates promptly once available. 2. Until patches are released, implement strict input validation and sanitization for all .vdhr files, rejecting files from untrusted or unauthenticated sources. 3. Employ network segmentation and isolate systems processing biosignal data to limit exposure to potentially malicious inputs. 4. Use application-level sandboxing or containerization to restrict the impact of any successful exploitation. 5. Conduct thorough code reviews and static analysis on any custom integrations with libbiosig to identify and remediate unsafe memory handling. 6. Educate staff on the risks of processing unverified biosignal files and enforce policies restricting file sources. 7. Implement robust logging and monitoring to detect anomalous activity related to biosignal data processing. 8. Coordinate with vendors and partners to ensure they are aware of the vulnerability and mitigation steps.

Description

A double-free vulnerability exists in the BrainVision ASCII Header Parsing functionality of The Biosig Project libbiosig 2.5.0 and Master Branch (ab0ee111). 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…