An out-of-bounds read vulnerability in GPAC 2.4.0 poses a critical risk of service disruption through crafted file processing.

This is an out-of-bounds read vulnerability within the GSF demuxer filter. The flaw is remotely exploitable by an unauthenticated attacker who provides a maliciously crafted .gsf file to the application.

Successful exploitation of this vulnerability results in a Denial of Service, effectively crashing the GPAC component. Given the CVSS score of 7.5, this high-severity flaw threatens the availability of multimedia processing pipelines, potentially leading to significant operational downtime for systems relying on this software for media ingestion or transcoding.

Immediate Action: Users should restrict the processing of untrusted .gsf files until an official patch is released by the vendor. Monitor vendor security advisories for the release of a corrected version of the GPAC software.

Proactive Monitoring: Security teams should monitor system logs for abnormal termination events or crashes associated with the GPAC process. Reviewing input file sources and implementing file validation protocols can help identify potentially malicious files before they reach the demuxer.

Compensating Controls: Deploying sandboxing or containerization for the GPAC processing environment can limit the impact of a crash to an isolated instance. Additionally, implement strict file size and format validation at the application gateway to drop suspicious media files.

Public Exploit Available: Yes, a proof-of-concept exists as documented in the research write-up provided in the references.

The presence of a public proof-of-concept elevates the risk profile of this vulnerability. Organizations should prioritize isolating systems that handle external media files and maintain vigilance for vendor-provided updates to address this out-of-bounds read flaw. Applying updates as soon as they become available is the only definitive method to resolve this security defect.