Resource exhaustion via leaked PID properties
Published Mar 27, 2023 · Updated Feb 19, 2025
Uncontrolled resource consumption in GPAC before 2.4.0 allows local users to exhaust memory by DASH-segmenting crafted media input. During PID instance swapping, gf_filter_pid_configure detaches property objects without decrementing their reference count, preventing their release. Triggering requires local MP4Box execution on attacker-controlled input; sustained allocation exhausts memory and interrupts the process.
Summary
What happened
Uncontrolled resource consumption in GPAC before 2.4.0 allows local users to exhaust memory by DASH-segmenting crafted media input. During PID instance swapping, gf_filter_pid_configure detaches property objects without decrementing their reference count, preventing their release. Triggering requires local MP4Box execution on attacker-controlled input; sustained allocation exhausts memory and interrupts the process.
The record
- CVE
- CVE-2023-1654
- Published
- Mar 27, 2023
- Updated
- Feb 19, 2025
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-400, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 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=unspecified <2.4.0
What conditions does exploitation require?
What is affected?
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
- MP4Box DASHer memory-leak 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