Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-59728: CWE-787 Out-of-bounds Write in FFmpeg MPEG-DASH

0
High
VulnerabilityCVE-2025-59728cvecve-2025-59728cwe-787
Published: Mon Oct 06 2025 (10/06/2025, 08:08:27 UTC)
Source: CVE Database V5
Vendor/Project: FFmpeg
Product: MPEG-DASH

Description

When calculating the content path in handling of MPEG-DASH manifests, there's an out-of-bounds NUL-byte write one byte past the end of the buffer.When we call xmlNodeGetContent below [0], it returns a buffer precisely allocated to match the string length, using strdup internally. If this buffer is not an empty string, it is assigned to root_url at [1].If the last (non-NUL) byte in this buffer is not '/' then we append '/' in-place at [2]. This will write two bytes into the buffer, starting at the last valid byte in the buffer, writing the NUL byte beyond the end of the allocated buffer. We recommend upgrading to version 8.0 or beyond.

AI-Powered Analysis

AILast updated: 10/06/2025, 08:47:57 UTC

Technical Analysis

CVE-2025-59728 is a vulnerability classified under CWE-787 (Out-of-bounds Write) found in FFmpeg's handling of MPEG-DASH manifests. Specifically, when FFmpeg processes the content path from an MPEG-DASH manifest, it calls xmlNodeGetContent, which returns a buffer allocated exactly to the string length using strdup. If this buffer is not empty and the last character is not a '/', the code attempts to append a '/' character in-place. This operation writes two bytes starting at the last valid byte of the buffer: the '/' character and a terminating NUL byte. Since the buffer was allocated precisely to the string length, this results in a NUL-byte write one byte beyond the allocated memory, causing an out-of-bounds write. This memory corruption can lead to undefined behavior, including potential arbitrary code execution or denial of service. The vulnerability affects FFmpeg version 7.1.1 and specific commits prior to version 8.0, which contains the fix. The CVSS 4.0 vector indicates the attack requires adjacent network access (AV:A), high attack complexity (AC:H), no privileges required (PR:L), no user interaction (UI:N), and impacts confidentiality, integrity, and availability with high scope changes (VC:H, VI:H, SC:H, SI:H). No known exploits have been reported in the wild yet, but the high severity score underscores the importance of mitigation. This vulnerability is particularly relevant for applications and services that use FFmpeg to process MPEG-DASH streaming content, common in media streaming platforms and broadcasting services.

Potential Impact

For European organizations, the impact of CVE-2025-59728 can be significant, especially those involved in media streaming, broadcasting, and content delivery networks that utilize FFmpeg for MPEG-DASH processing. Successful exploitation could lead to memory corruption, enabling attackers to execute arbitrary code, potentially compromising system confidentiality and integrity. This could result in unauthorized access to sensitive media content, disruption of streaming services, or broader network compromise if the affected systems are part of critical infrastructure. The high CVSS score reflects the potential for widespread impact, particularly in environments where FFmpeg is integrated into automated media processing pipelines. Given the vulnerability requires only adjacent network access and low privileges, attackers within the same network segment could exploit it without user interaction, increasing risk in shared or cloud environments. The absence of known exploits in the wild currently provides a window for proactive mitigation, but the potential consequences warrant urgent attention.

Mitigation Recommendations

European organizations should immediately upgrade FFmpeg to version 8.0 or later, where this vulnerability is patched. For environments where immediate upgrade is not feasible, organizations should implement network segmentation to limit adjacent network access to systems processing MPEG-DASH content. Monitoring and logging of FFmpeg processes and network traffic for unusual activity related to MPEG-DASH manifest handling can help detect exploitation attempts. Additionally, applying strict input validation and sandboxing FFmpeg processes can reduce the risk of memory corruption leading to code execution. Organizations should also review and restrict privileges of users and services interacting with FFmpeg to minimize the attack surface. Regular vulnerability scanning and penetration testing focused on media processing components can help identify residual risks. Finally, maintaining up-to-date threat intelligence feeds will assist in early detection of any emerging exploits targeting this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Google
Date Reserved
2025-09-19T08:11:37.549Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68e382204a42da91e7586492

Added to database: 10/6/2025, 8:47:28 AM

Last enriched: 10/6/2025, 8:47:57 AM

Last updated: 10/7/2025, 1:39:04 PM

Views: 14

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats