FFmpeg 2.1 Uninitialized Memory libavcodec/vc1.c bitplane_decoding memory corruption

Summaryinfo

A vulnerability was found in FFmpeg 2.1. It has been classified as critical. This vulnerability affects the function bitplane_decoding of the file libavcodec/vc1.c of the component Uninitialized Memory Handler. The manipulation leads to memory corruption. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in FFmpeg 2.1 (Multimedia Processing Software) and classified as very critical. This issue affects the function bitplane_decoding of the file libavcodec/vc1.c of the component Uninitialized Memory Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.

The issue has been introduced in 10/29/2013. The weakness was disclosed 12/14/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/vc1: fix DIFF2/NORM2 with width<=16 as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release has been coordinated in cooperation with the project team. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/17/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 (101344†). The entries VDB-11599, VDB-11598, VDB-11596 and VDB-11595 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Multimedia Processing Software

Name

• FFmpeg

Version

• 2.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 the best quality for vulnerability data then you always have to consider VulDB.

Discussion