Gentoo: GLSA-201702-11: GNU C Library: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in the GNU C Library. Please review the CVE identifiers referenced below for details.
Resolution
All GNU C Library users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-libs/glibc-2.23-r3"
References
[ 1 ] CVE-2014-9761 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-9761 [ 2 ] CVE-2015-5277 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-5277 [ 3 ] CVE-2015-8776 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8776 [ 4 ] CVE-2015-8777 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8777 [ 5 ] CVE-2015-8778 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8778 [ 6 ] CVE-2015-8779 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8779 [ 7 ] CVE-2016-1234 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1234 [ 8 ] CVE-2016-3075 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-3075
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201702-11
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.
Synopsis
Multiple vulnerabilities have been found in the GNU C Library, the worst of which allows context-dependent attackers to execute arbitrary code.
Background
The GNU C library is the standard C library used by Gentoo Linux systems.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-libs/glibc < 2.23-r3 >= 2.23-r3
Impact
===== A context-dependent attacker could possibly execute arbitrary code with the privileges of the process, disclose sensitive information, or cause a Denial of Service condition via multiple vectors.
Workaround
There is no known workaround at this time.