SB2017010315 - Multiple vulnerabilities in FFmpeg
Published: January 3, 2017 Updated: June 8, 2025
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 2 secuirty vulnerabilities.
1) Buffer overflow (CVE-ID: CVE-2014-7937)
The vulnerability allows a remote non-authenticated attacker to read and manipulate data.
Multiple off-by-one errors in libavcodec/vorbisdec.c in FFmpeg before 2.4.2, as used in Google Chrome before 40.0.2214.91, allow remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted Vorbis I data.
2) Buffer overflow (CVE-ID: CVE-2014-8542)
The vulnerability allows a remote non-authenticated attacker to read and manipulate data.
libavcodec/utils.c in FFmpeg before 2.4.2 omits a certain codec ID during enforcement of alignment, which allows remote attackers to cause a denial of service (out-of-bounds access) or possibly have unspecified other impact via crafted JV data.
Remediation
Install update from vendor's website.
References
- http://git.videolan.org/?p=ffmpeg.git;a=commit;h=8c50704ebf1777bee76772c4835d9760b3721057
- http://googlechromereleases.blogspot.com/2015/01/stable-update.html
- http://lists.opensuse.org/opensuse-security-announce/2015-03/msg00005.html
- http://rhn.redhat.com/errata/RHSA-2015-0093.html
- http://secunia.com/advisories/62383
- http://secunia.com/advisories/62575
- http://secunia.com/advisories/62665
- http://security.gentoo.org/glsa/glsa-201502-13.xml
- http://www.securityfocus.com/bid/72288
- http://www.securitytracker.com/id/1031623
- http://www.ubuntu.com/usn/USN-2476-1
- https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/d4608b7c83f56b17f14fdd94990341f62bb52f92
- https://code.google.com/p/chromium/issues/detail?id=419060
- https://security.gentoo.org/glsa/201603-06
- http://git.videolan.org/?p=ffmpeg.git;a=commit;h=105654e376a736d243aef4a1d121abebce912e6b
- http://www.ffmpeg.org/security.html
- http://www.ubuntu.com/usn/USN-2534-1
- https://lists.debian.org/debian-lts-announce/2019/02/msg00005.html