FFmpeg 1.1 Next/Last Picture Initialization libavcodec/h264.c memory corruption

Summaryinfo

A vulnerability was found in FFmpeg 1.1 and classified as critical. This vulnerability affects unknown code of the file libavcodec/h264.c of the component Next/Last Picture Initialization Handler. Executing a manipulation can lead to memory corruption. No exploit exists. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability classified as very critical was found in FFmpeg 1.1 (Multimedia Processing Software). This vulnerability affects an unknown code of the file libavcodec/h264.c of the component Next/Last Picture Initialization Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.

The issue has been introduced in 01/06/2013. The weakness was disclosed 02/21/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as h264: move next/last picture init to decode_slice_header as confirmed git commit (GIT Repository). The advisory is available at git.videolan.org. The public release has been coordinated in cooperation with the vendor. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/15/2019).

The vulnerability was handled as a non-public zero-day exploit for at least 46 days. During that time the estimated underground price was around $0-$5k.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (98785†). The entries VDB-10881, VDB-10880, VDB-10879 and VDB-10878 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• FFmpeg 1.1
• Libav 9.1

Productinfo

Type

• Multimedia Processing Software

Name

• FFmpeg

Version

• 1.1

License

• open-source

Website

• Product: https://ffmpeg.org/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion