From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201801-03 ] Chromium, Google Chrome: Multiple vulnerabilities
Date: Sun, 07 Jan 2018 18:22:46 -0500 [thread overview]
Message-ID: <2069448.XMbo7u3WEZ@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2637 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201801-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Chromium, Google Chrome: Multiple vulnerabilities
Date: January 07, 2018
Bugs: #640334, #641376
ID: 201801-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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 < 63.0.3239.108 >= 63.0.3239.108
2 www-client/google-chrome
< 63.0.3239.108 >= 63.0.3239.108
-------------------------------------------------------------------
2 affected packages
Description
===========
Multiple vulnerabilities have been discovered in Chromium and Google
Chrome. Please review the CVE identifiers referenced below 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 are no known workarounds at this time.
Resolution
==========
All Chromium users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=www-client/chromium-63.0.3239.108"
All Google Chrome users should upgrade to the latest version:
# emerge --sync
# emerge -a --oneshot -v ">=www-client/google-chrome-63.0.3239.108"
References
==========
[ 1 ] CVE-2017-15407
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15407
[ 2 ] CVE-2017-15408
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15408
[ 3 ] CVE-2017-15409
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15409
[ 4 ] CVE-2017-15410
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15410
[ 5 ] CVE-2017-15411
[-- Attachment #1.2: Type: text/html, Size: 33022 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-01-07 23:24 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=2069448.XMbo7u3WEZ@localhost.localdomain \
--to=bman@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@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