Gentoo: GLSA-202006-17: FAAD2: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in FAAD2. Please review the CVE identifiers referenced below for details.
Resolution
All FAAD2 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=media-libs/faad2-2.9.0"
References
[ 1 ] CVE-2018-19502 https://nvd.nist.gov/vuln/detail/CVE-2018-19502 [ 2 ] CVE-2018-19503 https://nvd.nist.gov/vuln/detail/CVE-2018-19503 [ 3 ] CVE-2018-19504 https://nvd.nist.gov/vuln/detail/CVE-2018-19504 [ 4 ] CVE-2018-20194 https://nvd.nist.gov/vuln/detail/CVE-2018-20194 [ 5 ] CVE-2018-20195 https://nvd.nist.gov/vuln/detail/CVE-2018-20195 [ 6 ] CVE-2018-20196 https://nvd.nist.gov/vuln/detail/CVE-2018-20196 [ 7 ] CVE-2018-20197 https://nvd.nist.gov/vuln/detail/CVE-2018-20197 [ 8 ] CVE-2018-20198 https://nvd.nist.gov/vuln/detail/CVE-2018-20198 [ 9 ] CVE-2018-20199 https://nvd.nist.gov/vuln/detail/CVE-2018-20199 [ 10 ] CVE-2018-20357 https://nvd.nist.gov/vuln/detail/CVE-2018-20357 [ 11 ] CVE-2018-20358 https://nvd.nist.gov/vuln/detail/CVE-2018-20358 [ 12 ] CVE-2018-20359 https://nvd.nist.gov/vuln/detail/CVE-2018-20359 [ 13 ] CVE-2018-20360 https://nvd.nist.gov/vuln/detail/CVE-2018-20...
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202006-17
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
Background
FAAD2 is an open source MPEG-4 and MPEG-2 AAC decoder.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 media-libs/faad2 < 2.9.0 >= 2.9.0
Impact
===== Please review the referenced CVE identifiers for details.
Workaround
There is no known workaround at this time.