The adpcm_decode_frame function in adpcm.c in libavcodec in FFmpeg before 0.9.1 and in Libav 0.5.x before 0.5.9, 0.6.x before 0.6.6, 0.7.x before 0.7.6, and 0.8.x before 0.8.3 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via an ADPCM file with the number of channels not equal to two.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
http://www.ubuntu.com/usn/USN-1479-1 | vendor advisory |
http://www.openwall.com/lists/oss-security/2012/02/14/4 | mailing list |
https://ffmpeg.org/trac/ffmpeg/ticket/794 | vendor advisory |
http://www.debian.org/security/2012/dsa-2494 | vendor advisory |
http://git.videolan.org/?p=ffmpeg.git%3Ba=commit%3Bh=608708009f69ba4cecebf05120c696167494c897 | |
http://libav.org/ | vendor advisory |
http://ffmpeg.org/security.html | |
https://exchange.xforce.ibmcloud.com/vulnerabilities/78932 | vdb entry |