CVE-2024-57184
📋 TL;DR
A heap-based buffer overflow vulnerability exists in GPAC v0.8.0's MP4Box tool when processing crafted MP4 files. This can cause denial of service (crash) and potentially allow arbitrary code execution. Users and systems processing untrusted MP4 files with GPAC are affected.
💻 Affected Systems
- GPAC
- MP4Box
📦 What is this software?
Gpac by Gpac
⚠️ Risk & Real-World Impact
Worst Case
Remote code execution leading to complete system compromise if heap manipulation succeeds.
Likely Case
Denial of service (application crash) when processing malicious MP4 files.
If Mitigated
Application crash with no further impact if exploit fails or is contained.
🎯 Exploit Status
Requires crafting a malicious MP4 file; heap manipulation for RCE is complex but DoS is straightforward.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Fixed in commit 8c5e847185d74462d674ee7d28fb46c29dae6dd2
Vendor Advisory: https://github.com/gpac/gpac/issues/1421
Restart Required: No
Instructions:
1. Update GPAC to latest version from official repository. 2. Rebuild from source if using custom builds. 3. Replace MP4Box binary with patched version.
🔧 Temporary Workarounds
Input validation
allValidate MP4 files before processing with GPAC tools
Sandbox execution
linuxRun MP4Box in container or sandboxed environment
docker run --rm -v $(pwd):/data gpac/gpac mp4box [options]
🧯 If You Can't Patch
- Restrict MP4 file processing to trusted sources only
- Implement application allowlisting to prevent unauthorized GPAC/MP4Box execution
🔍 How to Verify
Check if Vulnerable:
Check GPAC version: mp4box -version | grep 'GPAC'Check Version:
mp4box -version 2>&1 | head -1Verify Fix Applied:
Verify commit hash includes 8c5e847 or check version is newer than v0.8.0📡 Detection & Monitoring
Log Indicators:
- GPAC/MP4Box crash logs
- Segmentation fault errors
- Abnormal process termination
Network Indicators:
- Unusual MP4 file uploads to processing systems
SIEM Query:
process_name:"mp4box" AND (event_type:"crash" OR exit_code:139)