A vulnerability, which was classified as very critical, was found in FFmpeg 2.1 (Multimedia Processing Software). This affects the function hnm_decode_frame of the file libavcodec/hnm4video.c of the component Coded Frame Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.

The issue has been introduced in 10/29/2013. The weakness was disclosed 11/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/hnm4video: allocate frame only when theres a coded frame 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 exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for 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 24 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 entries 11401, 11400, 11399 and 11398 are pretty similar.

Affected

• FFmpeg 2.1
• Libav 0.8.9

Productinfo

Type

• Multimedia Processing Software

Name

• FFmpeg

Version

• 2.1

License

• open-source

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion