CVE-2025-55642
Analyzed Analyzed - Analysis Complete

Floating Point Exception in GPAC MP4Box

Vulnerability report for CVE-2025-55642, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-15

Last updated on: 2026-06-16

Assigner: MITRE

Description

GPAC MP4Box v2.4 was discovered to contain a floating point exception in the avidmx_process function (isomedia/isom_write.c).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-15
Last Modified
2026-06-16
Generated
2026-07-06
AI Q&A
2026-06-16
EPSS Evaluated
2026-07-04
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
gpac gpac to 26.02.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-369 The product divides a value by zero.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Compliance Impact

The provided information does not specify any direct impact of the CVE-2025-55642 vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Impact Analysis

This vulnerability can potentially cause the affected software to crash or behave unexpectedly due to the floating point exception. Such behavior might be exploited by an attacker to disrupt normal operations or cause denial of service conditions when processing certain media files.

Executive Summary

CVE-2025-55642 is a vulnerability found in GPAC MP4Box version 2.4. It involves a floating point exception occurring in the avidmx_process function within the isomedia/isom_write.c file. This type of exception typically arises from an invalid arithmetic operation, such as division by zero.

Detection Guidance

This vulnerability can be detected by monitoring for crashes or floating point exceptions in GPAC MP4Box when processing media files, especially AVI-like files with suspicious or invalid frame-count metadata.

Specifically, the issue occurs in the avidmx_process function when a crafted file declares zero frames, causing a divide-by-zero error.

Detection can involve running MP4Box with AddressSanitizer enabled to catch floating point exceptions or crashes triggered by malformed input files.

Suggested commands include using MP4Box to process suspect media files and observing for crashes or exceptions, for example:

  • Run MP4Box on suspicious AVI-like files: `MP4Box -dash 1000 suspicious_file.avi`
  • Use AddressSanitizer to detect floating point exceptions during processing: `ASAN_OPTIONS=detect_divide_by_zero=1 MP4Box -dash 1000 suspicious_file.avi`

Additionally, monitoring logs for crashes or exceptions related to MP4Box can help identify exploitation attempts.

Mitigation Strategies

Immediate mitigation steps include avoiding processing untrusted or suspicious AVI-like media files with GPAC MP4Box until a patch is applied.

Restrict access to MP4Box to trusted users and environments to reduce the risk of malicious file processing.

Monitor for updates or patches from the GPAC project addressing this divide-by-zero vulnerability and apply them as soon as they become available.

If possible, use runtime protections such as AddressSanitizer to detect and prevent crashes caused by malformed inputs during testing.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-55642. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart