Code execution via unchecked EGI event count
Published Feb 20, 2024 · Updated Nov 4, 2025
Heap-based buffer overflow in The BioSig Project libbiosig 2.5.0 allows remote attackers to execute arbitrary code via a crafted .egi file. In sopen_extended, an unbounded EGI event count drives pointer writes beyond the fixed 257-entry CodeDesc heap allocation. A consuming process must parse the file with 2.5.0 or Master Branch (ab0ee111), after which the overwrite can execute code in that process.
Summary
What happened
Heap-based buffer overflow in The BioSig Project libbiosig 2.5.0 allows remote attackers to execute arbitrary code via a crafted .egi file. In sopen_extended, an unbounded EGI event count drives pointer writes beyond the fixed 257-entry CodeDesc heap allocation. A consuming process must parse the file with 2.5.0 or Master Branch (ab0ee111), after which the overwrite can execute code in that process.
The record
- CVE
- CVE-2024-21795
- Published
- Feb 20, 2024
- Updated
- Nov 4, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=40
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- TALOS-2024-1920 technical proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo