Heap Corruption Vulnerability in FFmpeg

ffmpeg Updated 02 Oct 2025

Summary

17/02/2017
N/A
Yes i
Medium
5.5

CVE-2017-5024: FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted video file. Affects ffmpeg versions < 2.8.11-r0. Fixed in 2.8.11-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

FFmpeg is a popular open-source multimedia framework used for decoding, encoding, and streaming audio and video files. It is widely used in various applications and platforms. However, a vulnerability has been discovered in FFmpeg versions prior to 56.0.2924.76 for Linux, Windows, and Mac. This vulnerability can potentially be exploited by a remote attacker through a crafted video file, leading to heap corruption.

Vulnerability Detail

The vulnerability in FFmpeg arises from a failure to perform proper bounds checking. This allows a remote attacker to manipulate the video file in such a way that it triggers heap corruption. Heap corruption can lead to various security issues, including remote code execution, denial of service, or information disclosure. The impact of this vulnerability depends on the specific usage of FFmpeg in the affected system.

How To Fix

Minimum fixed version

2.8.11-r0

This is the first release that contains the fix.

sudo apk add --upgrade ffmpeg

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update FFmpeg to the fixed version as soon as possible to protect against potential exploitation.

Conclusion

The heap corruption vulnerability in FFmpeg can have serious security implications for systems utilizing this multimedia framework. It is crucial to update FFmpeg to the latest fixed version to mitigate the risk of exploitation. For further assistance and support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for ffmpeg →

Share this vulnerability

FAQ

FFmpeg is an open-source multimedia framework used for audio and video processing, encoding, decoding, and streaming.

This vulnerability can be exploited by a remote attacker through a specially crafted video file, potentially leading to heap corruption and various security issues.

Heap corruption can result in remote code execution, denial of service, or information disclosure, depending on the specific circumstances and usage of the affected software.

Updating FFmpeg to version 56.0.2924.76 or later is the recommended solution. Regularly updating FFmpeg to the latest stable release is also important for receiving security patches and bug fixes.

No known workaround exists for this vulnerability. Updating FFmpeg to the fixed version is the only effective solution.

Related vulnerabilities

Recent vulnerabilities recorded for ffmpeg.

How To Fix

Minimum fixed version

2.8.11-r0

This is the first release that contains the fix.

sudo apk add --upgrade ffmpeg

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback