From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201804-02 ] glibc: Multiple vulnerabilities
Date: Tue, 3 Apr 2018 21:54:59 -0400 [thread overview]
Message-ID: <20180404015459.GB30411@monkey> (raw)
[-- Attachment #1: Type: text/plain, Size: 3138 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201804-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: glibc: Multiple vulnerabilities
Date: April 04, 2018
Bugs: #632556, #634920, #635118, #641644, #644278, #646490, #646492
ID: 201804-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in glibc, the worst of which
could allow remote attackers to execute arbitrary code.
Background
==========
glibc is a package that contains the GNU C library.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 sys-libs/glibc < 2.25-r11 >= 2.25-r11
Description
===========
Multiple vulnerabilities have been discovered in glibc. Please review
the CVE identifiers referenced below for details.
Impact
======
An attacker could possibly execute arbitrary code, escalate privileges,
cause a Denial of Service condition, or have other unspecified impacts.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All glibc users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-libs/glibc-2.25-r11"
References
==========
[ 1 ] CVE-2017-14062
https://nvd.nist.gov/vuln/detail/CVE-2017-14062
[ 2 ] CVE-2017-15670
https://nvd.nist.gov/vuln/detail/CVE-2017-15670
[ 3 ] CVE-2017-15671
https://nvd.nist.gov/vuln/detail/CVE-2017-15671
[ 4 ] CVE-2017-15804
https://nvd.nist.gov/vuln/detail/CVE-2017-15804
[ 5 ] CVE-2017-16997
https://nvd.nist.gov/vuln/detail/CVE-2017-16997
[ 6 ] CVE-2018-1000001
https://nvd.nist.gov/vuln/detail/CVE-2018-1000001
[ 7 ] CVE-2018-6485
https://nvd.nist.gov/vuln/detail/CVE-2018-6485
[ 8 ] CVE-2018-6551
https://nvd.nist.gov/vuln/detail/CVE-2018-6551
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201804-02
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.
License
=======
Copyright 2018 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-04-04 2:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180404015459.GB30411@monkey \
--to=bman@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox