CVE-2024-24267
📋 TL;DR
This vulnerability in GPAC multimedia framework allows memory exhaustion through a memory leak in the gf_fileio_from_blob function. Attackers could cause denial of service by repeatedly triggering the leak, potentially crashing affected systems. Users and applications processing multimedia files with vulnerable GPAC versions are affected.
💻 Affected Systems
- GPAC Multimedia Framework
📦 What is this software?
Gpac by Gpac
⚠️ Risk & Real-World Impact
Worst Case
Sustained exploitation could lead to complete system memory exhaustion, causing system crashes, service disruption, and potential data loss in affected applications.
Likely Case
Denial of service through gradual memory consumption, potentially crashing multimedia processing applications or services using GPAC.
If Mitigated
Limited impact with proper memory monitoring and restart policies; isolated to specific multimedia processing functions.
🎯 Exploit Status
Memory leak vulnerabilities typically require repeated triggering; no public exploit code identified in references.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: v2.4.0
Vendor Advisory: https://github.com/gpac/gpac/commit/d28d9ba45cf4f628a7b2c351849a895e6fcf2234
Restart Required: Yes
Instructions:
1. Download GPAC v2.4.0 or later from official repository. 2. Uninstall current version. 3. Install patched version. 4. Restart any services using GPAC.
🔧 Temporary Workarounds
Memory Limit Enforcement
linuxLimit memory usage of GPAC processes to contain potential memory exhaustion
ulimit -v 1048576
systemctl set-property gpac.service MemoryMax=1G
🧯 If You Can't Patch
- Implement strict input validation for multimedia files processed by GPAC
- Monitor memory usage of GPAC processes and restart when thresholds exceeded
🔍 How to Verify
Check if Vulnerable:
Check GPAC version: gpac -version | grep 'GPAC'Check Version:
gpac -versionVerify Fix Applied:
Verify version is v2.4.0 or later: gpac -version📡 Detection & Monitoring
Log Indicators:
- Abnormal memory consumption patterns
- GPAC process crashes
- Repeated file processing errors
Network Indicators:
- Unusual multimedia file upload patterns
- Repeated requests to multimedia processing endpoints
SIEM Query:
Process:gpac AND (MemoryUsage > 90% OR ExitCode != 0)🔗 References
- https://github.com/NixOS/nixpkgs/pull/305402
- https://github.com/gpac/gpac/commit/d28d9ba45cf4f628a7b2c351849a895e6fcf2234
- https://github.com/gpac/gpac/issues/2571
- https://github.com/yinluming13579/gpac_defects/blob/main/gpac_3.md
- https://github.com/gpac/gpac/commit/d28d9ba45cf4f628a7b2c351849a895e6fcf2234
- https://github.com/gpac/gpac/issues/2571
- https://github.com/yinluming13579/gpac_defects/blob/main/gpac_3.md
