A vulnerability was found in FFmpeg up to 1.2.1 (Multimedia Processing Software). It has been rated as problematic. This issue affects the function decode_p_block of the file libavcodec/4xm.c. 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.

The weakness was shared 06/09/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as wavpack: use bytestream2 in wavpack_decode_block as confirmed git commit (GIT Repository). It is possible to read the advisory at git.videolan.org. The vendor cooperated in the coordination of the public release. The exploitation is known to be difficult. The attack needs to approached within the local network. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Applying the patch wavpack: use bytestream2 in wavpack_decode_block is able to eliminate this problem. The bugfix is ready for download at git.libav.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The entries 9363, 9362, 9360 and 9358 are related to this item.

Affected

• FFmpeg
• Libav

Productinfo

Type

• Multimedia Processing Software

Name

• FFmpeg

Version

• 1.2.0
• 1.2.1

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion