Memory exhaustion via unreleased PID properties
Published Feb 5, 2024 · Updated May 9, 2025
Memory leak in GPAC 2.2.1 allows remote attackers to exhaust process memory by repeatedly triggering PID property merging. In gf_filter_pid_merge_properties_internal, check_new_pid_props allocates dst_props through gf_props_new, but an early return at line 6131 omits its release. No privileges or user interaction are required; repeated triggers consume process memory, with no reported data disclosure or modification.
Summary
What happened
Memory leak in GPAC 2.2.1 allows remote attackers to exhaust process memory by repeatedly triggering PID property merging. In gf_filter_pid_merge_properties_internal, check_new_pid_props allocates dst_props through gf_props_new, but an early return at line 6131 omits its release. No privileges or user interaction are required; repeated triggers consume process memory, with no reported data disclosure or modification.
The record
- CVE
- CVE-2024-24265
- Published
- Feb 5, 2024
- Updated
- May 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- May 9, 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 dst_props memory-leak proof of conceptproof 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