metadata/glsa/glsa-201801-03.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201801-03">
  <title>Chromium, Google Chrome: Multiple vulnerabilities </title>
  <synopsis>Multiple vulnerabilities have been found in Chromium and Google
    Chrome, the worst of which could result in the execution of arbitrary code.
  </synopsis>
  <product type="ebuild">chromium,google-chrome</product>
  <announced>2018-01-07</announced>
  <revised>2018-01-07: 1</revised>
  <bug>640334</bug>
  <bug>641376</bug>
  <access>local, remote</access>
  <affected>
    <package name="www-client/chromium" auto="yes" arch="*">
      <unaffected range="ge">63.0.3239.108</unaffected>
      <vulnerable range="lt">63.0.3239.108</vulnerable>
    </package>
    <package name="www-client/google-chrome" auto="yes" arch="*">
      <unaffected range="ge">63.0.3239.108</unaffected>
      <vulnerable range="lt">63.0.3239.108</vulnerable>
    </package>
  </affected>
  <background>
    <p>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.
    </p>
    
    <p>Google Chrome is one fast, simple, and secure browser for all your
      devices
    </p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in Chromium and Google
      Chrome. Please review the CVE identifiers referenced below for details.
    </p>
  </description>
  <impact type="normal">
    <p>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.
    </p>
  </impact>
  <workaround>
    <p>There are no known workarounds at this time.</p>
  </workaround>
  <resolution>
    <p>All Chromium users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose
      "&gt;=www-client/chromium-63.0.3239.108"
    </code>
    
    <p>All Google Chrome users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose
      "&gt;=www-client/google-chrome-63.0.3239.108"
    </code>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15407">
      CVE-2017-15407
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15408">
      CVE-2017-15408
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15409">
      CVE-2017-15409
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15410">
      CVE-2017-15410
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15411">
      CVE-2017-15411
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15412">
      CVE-2017-15412
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15413">
      CVE-2017-15413
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15415">
      CVE-2017-15415
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15416">
      CVE-2017-15416
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15417">
      CVE-2017-15417
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15418">
      CVE-2017-15418
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15419">
      CVE-2017-15419
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15420">
      CVE-2017-15420
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15422">
      CVE-2017-15422
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15423">
      CVE-2017-15423
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15424">
      CVE-2017-15424
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15425">
      CVE-2017-15425
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15426">
      CVE-2017-15426
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15427">
      CVE-2017-15427
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-15429">
      CVE-2017-15429
    </uri>
    <uri link="https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html">
      Google Chrome Release 20171206
    </uri>
    <uri link="https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop_14.html">
      Google Chrome Release 20171214
    </uri>
  </references>
  <metadata tag="requester" timestamp="2018-01-05T05:50:33Z">jmbailey</metadata>
  <metadata tag="submitter" timestamp="2018-01-07T23:22:12Z">jmbailey</metadata>
</glsa>