* [gentoo-announce] [ GLSA 201802-02 ] Chromium, Google Chrome: Multiple vulnerabilities
@ 2018-02-19 23:20 Christopher Díaz Riveros
0 siblings, 0 replies; only message in thread
From: Christopher Díaz Riveros @ 2018-02-19 23:20 UTC (permalink / raw
To: gentoo-announce
[-- Attachment #1: Type: text/plain, Size: 5250 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201802-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Chromium, Google Chrome: Multiple vulnerabilities
Date: February 19, 2018
Bugs: #647124, #647636
ID: 201802-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in Chromium and Google Chrome,
the worst of which could result in the execution of arbitrary code.
Background
==========
Chromium is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.
Google Chrome is one fast, simple, and secure browser for all your
devices.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 www-client/chromium < 64.0.3282.167 >= 64.0.3282.167
2 www-client/google-chrome
< 64.0.3282.167 >= 64.0.3282.167
-------------------------------------------------------------------
2 affected packages
Description
===========
Multiple vulnerabilities have been discovered in Chromium and Google
Chrome. Please review the referenced CVE identifiers and Google Chrome
Releases for details.
Impact
======
A remote attacker could possibly execute arbitrary code with the
privileges of the process, cause a Denial of Service condition, bypass
content security controls, or conduct URL spoofing.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Chromium users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=www-client/chromium-64.0.3282.167"
All Google Chrome users should upgrade to the latest version:
# emerge --sync
# emerge -a --oneshot -v ">=www-client/google-chrome-64.0.3282.167"
References
==========
[ 1 ] CVE-2018-6031
https://nvd.nist.gov/vuln/detail/CVE-2018-6031
[ 2 ] CVE-2018-6032
https://nvd.nist.gov/vuln/detail/CVE-2018-6032
[ 3 ] CVE-2018-6033
https://nvd.nist.gov/vuln/detail/CVE-2018-6033
[ 4 ] CVE-2018-6034
https://nvd.nist.gov/vuln/detail/CVE-2018-6034
[ 5 ] CVE-2018-6035
https://nvd.nist.gov/vuln/detail/CVE-2018-6035
[ 6 ] CVE-2018-6036
https://nvd.nist.gov/vuln/detail/CVE-2018-6036
[ 7 ] CVE-2018-6037
https://nvd.nist.gov/vuln/detail/CVE-2018-6037
[ 8 ] CVE-2018-6038
https://nvd.nist.gov/vuln/detail/CVE-2018-6038
[ 9 ] CVE-2018-6039
https://nvd.nist.gov/vuln/detail/CVE-2018-6039
[ 10 ] CVE-2018-6040
https://nvd.nist.gov/vuln/detail/CVE-2018-6040
[ 11 ] CVE-2018-6041
https://nvd.nist.gov/vuln/detail/CVE-2018-6041
[ 12 ] CVE-2018-6042
https://nvd.nist.gov/vuln/detail/CVE-2018-6042
[ 13 ] CVE-2018-6043
https://nvd.nist.gov/vuln/detail/CVE-2018-6043
[ 14 ] CVE-2018-6045
https://nvd.nist.gov/vuln/detail/CVE-2018-6045
[ 15 ] CVE-2018-6046
https://nvd.nist.gov/vuln/detail/CVE-2018-6046
[ 16 ] CVE-2018-6047
https://nvd.nist.gov/vuln/detail/CVE-2018-6047
[ 17 ] CVE-2018-6048
https://nvd.nist.gov/vuln/detail/CVE-2018-6048
[ 18 ] CVE-2018-6049
https://nvd.nist.gov/vuln/detail/CVE-2018-6049
[ 19 ] CVE-2018-6050
https://nvd.nist.gov/vuln/detail/CVE-2018-6050
[ 20 ] CVE-2018-6051
https://nvd.nist.gov/vuln/detail/CVE-2018-6051
[ 21 ] CVE-2018-6052
https://nvd.nist.gov/vuln/detail/CVE-2018-6052
[ 22 ] CVE-2018-6053
https://nvd.nist.gov/vuln/detail/CVE-2018-6053
[ 23 ] CVE-2018-6054
https://nvd.nist.gov/vuln/detail/CVE-2018-6054
[ 24 ] CVE-2018-6056
https://nvd.nist.gov/vuln/detail/CVE-2018-6056
[ 25 ] Google Chrome Release 20180124
https://chromereleases.googleblog.com/2018/01/stable-channel-upd
ate-for-desktop_24.html
[ 26 ] Google Chrome Release 20180213
https://chromereleases.googleblog.com/2018/02/stable-channel-upd
ate-for-desktop_13.html
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201802-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: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 636 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-02-19 23:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-19 23:20 [gentoo-announce] [ GLSA 201802-02 ] Chromium, Google Chrome: Multiple vulnerabilities Christopher Díaz Riveros
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox