Skip to main content
Vulnerability Database/CVE-2025-60492

CVE-2025-60492: GPAC MP4Box Stack Overflow DoS Vulnerability

CVE-2025-60492 is a stack overflow vulnerability in GPAC MP4Box that enables attackers to cause denial of service through crafted MP4 files. This article covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-60492 Overview

CVE-2025-60492 is a stack overflow vulnerability in the gf_bifs_dec_node function located in /bifs/field_decode.c of GPAC Project/MP4Box before version 2.5. Attackers can trigger a Denial of Service (DoS) by supplying a crafted MP4 file to the vulnerable parser. The flaw is tracked as a stack-based buffer overflow weakness [CWE-121] and requires local user interaction, since the victim must open or process the malicious media file. GPAC is a widely used multimedia framework, and MP4Box is its command-line packaging and manipulation tool used in media production pipelines.

Critical Impact

A crafted MP4 file processed by MP4Box crashes the application through a stack overflow in the BIFS decoder, causing a denial-of-service condition.

Affected Products

  • GPAC Project MP4Box versions prior to 2.5
  • GPAC multimedia framework BIFS codec component (src/bifs/field_decode.c)
  • Applications and pipelines embedding the vulnerable GPAC BIFS decoder

Discovery Timeline

  • 2026-10-21 - CVE-2025-60492 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2025-60492

Vulnerability Analysis

The vulnerability resides in gf_bifs_dec_node, a function responsible for decoding Binary Format for Scenes (BIFS) nodes within MP4 containers. When MP4Box parses a specially crafted MP4 file, the decoder exceeds the available stack space, leading to a crash. The issue is categorized as a stack-based buffer overflow [CWE-121]. Exploitation produces a denial-of-service condition rather than code execution, consistent with the local attack vector and availability-only impact.

Root Cause

The root cause is unbounded or improperly bounded recursion or allocation on the stack during BIFS node decoding. Malformed node structures in the MP4 input drive the decoder into states that consume more stack than the runtime allows, terminating the process.

Attack Vector

An attacker crafts a malicious MP4 file and delivers it to a user or automated workflow that invokes MP4Box. Processing the file triggers the overflow in gf_bifs_dec_node, crashing the parser. The attack requires user interaction and local file processing but no authentication.

c
// Patch metadata from the upstream commit
// File: src/bifs/field_decode.c
- *            Copyright (c) Telecom ParisTech 2000-2023
+ *            Copyright (c) Telecom ParisTech 2000-2025

// File: include/gpac/internal/bifs_dev.h
- *            Copyright (c) Telecom ParisTech 2000-2012
+ *            Copyright (c) Telecom ParisTech 2000-2025
// Source: https://github.com/gpac/gpac/commit/8e7b9a3a04331286b89d1803c65a2d6edc11b4c4

Detection Methods for CVE-2025-60492

Indicators of Compromise

  • Unexpected crashes or segmentation faults of MP4Box or GPAC-linked processes when parsing MP4 input
  • Core dumps whose stack trace terminates inside gf_bifs_dec_node or field_decode.c
  • MP4 files from untrusted sources containing malformed BIFS scene nodes

Detection Strategies

  • Inventory systems running GPAC/MP4Box and flag any installation below version 2.5
  • Monitor media processing pipelines for repeated abnormal process terminations tied to MP4 ingestion
  • Scan file submission queues for MP4 files that fail validation against a reference parser

Monitoring Recommendations

  • Enable crash reporting (for example, systemd-coredump or Windows WER) on hosts that run MP4Box in batch jobs
  • Alert on process exit codes and signal-based terminations in media encoding workloads
  • Correlate media file ingestion events with subsequent MP4Box crashes in your SIEM

How to Mitigate CVE-2025-60492

Immediate Actions Required

  • Upgrade GPAC/MP4Box to version 2.5 or later on all systems that process untrusted MP4 content
  • Restrict MP4Box execution to trusted inputs and sandboxed service accounts
  • Validate the source and integrity of MP4 files before feeding them to automated pipelines

Patch Information

The GPAC maintainers addressed the issue in commit 8e7b9a3a04331286b89d1803c65a2d6edc11b4c4, which modifies src/bifs/field_decode.c and include/gpac/internal/bifs_dev.h. Users should update to GPAC 2.5 or newer. See the GPAC commit log and GitHub Issue #3324 for upstream details, and the GitHub PoC README for reproduction notes.

Workarounds

  • Run MP4Box inside a container or sandbox with resource and syscall limits to contain crashes
  • Disable or avoid BIFS decoding paths for untrusted MP4 inputs where possible
  • Enforce file-type and schema validation on MP4 uploads before invoking GPAC utilities
bash
# Verify installed MP4Box version and upgrade if below 2.5
MP4Box -version 2>&1 | head -n 1

# Example: run MP4Box with resource limits to contain DoS impact
ulimit -s 8192 -t 30 -v 1048576
MP4Box -info /path/to/untrusted.mp4

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.