Service interruption via unreleased gfio_blob allocation
Published Feb 5, 2024 · Updated Sep 15, 2025
Memory leakage in GPAC 2.2.1 allows remote attackers to interrupt service via input that makes GF_FileIO object creation fail. The gf_fileio_from_mem function allocates gfio_blob but returns without freeing it when gf_fileio_new fails. The failure path must be reached repeatedly to exhaust process memory, and no data disclosure or modification is reported.
Summary
What happened
Memory leakage in GPAC 2.2.1 allows remote attackers to interrupt service via input that makes GF_FileIO object creation fail. The gf_fileio_from_mem function allocates gfio_blob but returns without freeing it when gf_fileio_new fails. The failure path must be reached repeatedly to exhaust process memory, and no data disclosure or modification is reported.
The record
- CVE
- CVE-2024-24267
- Published
- Feb 5, 2024
- Updated
- Sep 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Sep 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- GPAC gfio_blob memory-leak technical demonstrationproof of concept · unverified
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