CVE-2025-55658: GPAC MP4Box v2.4 was discovered to contain a floating point exception in the gf_opus_parse_packet_header fu...
GPAC MP4Box v2.4 was discovered to contain a floating point exception in the gf_opus_parse_packet_header function (media_tools/av_parsers.c). bThis vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.
Security readout for executives and security teams
Plain-English summary
This CVE describes a crash condition in GPAC MP4Box v2.4 when handling a crafted MP4 file. The business impact is denial of service, not data theft or code execution based on the provided sources. Risk is highest for systems that process media files from users or partners.
Executive priority
Treat this as a moderate availability risk. Prioritize externally facing media-processing services first, especially where file parsing outages could affect customers, workflows, or automated pipelines.
Technical view
The issue is a floating point exception in gf_opus_parse_packet_header within media_tools/av_parsers.c. The CVSS 3.1 score is 6.5 with network attack vector, low complexity, no privileges required, user interaction required, and high availability impact only.
Likely exposure
Exposure is most likely where GPAC MP4Box v2.4 is installed or embedded in MP4 ingestion, validation, packaging, or analysis workflows. The CVE affected-product metadata is incomplete and lists vendor, product, and versions as n/a, so inventory confirmation is necessary.
Exploitation context
The sources state attackers can cause denial of service via a crafted MP4 file. The CVE is not listed as KEV, and the provided sources do not show active exploitation, public weaponization, or a vendor patch.
Researcher notes
Evidence is limited to the CVE description and one public reference. The affected metadata is not well populated. Validate the exact GPAC version and deployment path before declaring exposure or closure.
Mitigation direction
Identify systems using GPAC MP4Box v2.4 or bundled GPAC libraries.
Avoid processing untrusted MP4 files until vendor guidance is confirmed.
Sandbox or isolate media-processing jobs that handle external files.
Apply vendor updates or workarounds if GPAC publishes them.
Rate-limit and monitor upload or media-processing queues.
Validation and detection
Search asset inventories and build manifests for GPAC or MP4Box v2.4.
Review services that accept MP4 uploads from external users or partners.
Check crash logs for MP4Box failures during Opus-in-MP4 parsing.
Monitor GPAC and CVE records for corrected affected-version and patch details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1077: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1077 · source CWE mapping
Floating Point Comparison with Incorrect Operator
Floating Point Comparison with Incorrect Operator represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.