The cdg_decode_frame function in cdgraphics.c in libavcodec in FFmpeg before
1.2.1 does not validate the presence of non-header data in a buffer, which
allows remote attackers to cause a denial of service (out-of-bounds array
access and application crash) via crafted CD Graphics Video data.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3674
(From OE-Core master rev: f1721553a873b242bc26ad3e4d618aea39dfd507)
(From OE-Core rev: d4d908afca1c6ce64f05fabdadfcf86ab990dd0f)
Signed-off-by: Ming Liu <ming.liu@windriver.com>
Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pass --cpu to libav config when we're building ppc, or else there are
errors like:
You need a compiler that supports {} in AltiVec vector declarations.
Also patch libav configure to have knowledge of more ppc CPUs.
(From OE-Core rev: a825781fc822f4630bc29906ca1ca79b8fad4836)
Signed-off-by: Jesse Zhang <sen.zhang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The gst-ffmpeg build shows the following warning:
configure: WARNING: unrecognized options: --disable-yasm
which means that the following test in configure always fails and
--disable-yasm never gets passed to the embedded ffmpeg build:
'if test "x$disable_yasm" = "xyes"; then'
embffmpeg_configure_args="$embffmpeg_configure_args --disable-yasm"
commit 4d309730 ['gst-ffmpeg: configure-fix patch used wrong test']
actually fixed the obviously backwards syntax by reversing the test -
prior to that, --disable-yasm would always unconditionally be passed
into the embedded ffmpeg config.
This fixes things so that the variable actually exists and makes the
test meaningful.
(From OE-Core rev: da9515621134c26e54f43b96cdad0c6e6c5876bf)
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1.The included libav configure is not generated by autotools
modify recipe to use correct toolchain wrapper with configure
2.add bzip2 dependency explicitly.
or configure will detect whether libbz2 is installed, if bzip2
is triggered earlier then it will be detected, if not then won't
3.backport libav_e500mc.patch from upstream to patch configure to
disable-altivec if it is e500mc.
4.move the GSTREAMER_DEBUG to libav's configure, it is not the
option for the main configure.
(From OE-Core rev: a6384b2bd1d608506557ce151135edffa4cb5e0b)
Signed-off-by: Yao Zhao <yao.zhao@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A cmp instruction with two constants is invalid, therefore 'g' constraint
is not correct but must be "rm" instead.
(From OE-Core rev: 1161c40a26146629613bd6a17b263175a492b751)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch is to upgrade gst-ffmpeg to 0.10.13.
Some license files are changed because the folder "ffmpeg" disappears, and those license files under "libav" are the same. LICENSE is different because the word "ffmpeg" is changed into "libav" under the libav folder.
Again, gst-ffmpeg tar ball contains library libav itself. So the configure needs to disable yasm for x86.
(From OE-Core rev: 5c86f5506a060e2005fcdad0b46ca650598a94af)
Signed-off-by: Shane Wang <shane.wang@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ming Liu
Jesse Zhang
Tom Zanussi
Carlos Rafael Giani
Yao Zhao
Saul Wold
Khem Raj
Shane Wang