metadata/glsa/glsa-201704-02.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

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201704-02">
  <title>Chromium: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in the Chromium web
    browser, the worst of which allows remote attackers to execute arbitrary
    code.
  </synopsis>
  <product type="ebuild">chromium</product>
  <announced>2017-04-10</announced>
  <revised count="2">2017-04-14</revised>
  <bug>612190</bug>
  <bug>614276</bug>
  <access>remote</access>
  <affected>
    <package name="www-client/chromium" auto="yes" arch="*">
      <unaffected range="ge">57.0.2987.133</unaffected>
      <vulnerable range="lt">57.0.2987.133</vulnerable>
    </package>
  </affected>
  <background>
    <p>Chromium is the open-source web browser project behind Google Chrome</p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in the Chromium web
      browser. 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, obtain
      sensitive information, or bypass security restrictions.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround 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-57.0.2987.133"
    </code>
    
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5030">CVE-2017-5030</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5031">CVE-2017-5031</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5032">CVE-2017-5032</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5033">CVE-2017-5033</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5034">CVE-2017-5034</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5035">CVE-2017-5035</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5036">CVE-2017-5036</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5037">CVE-2017-5037</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5038">CVE-2017-5038</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5039">CVE-2017-5039</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5040">CVE-2017-5040</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5041">CVE-2017-5041</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5042">CVE-2017-5042</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5043">CVE-2017-5043</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5044">CVE-2017-5044</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5045">CVE-2017-5045</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5046">CVE-2017-5046</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5052">CVE-2017-5052</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5053">CVE-2017-5053</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5054">CVE-2017-5054</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5055">CVE-2017-5055</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5056">CVE-2017-5056</uri>
  </references>
  <metadata tag="requester" timestamp="2017-04-02T12:37:12Z">BlueKnight</metadata>
  <metadata tag="submitter" timestamp="2017-04-14T15:04:47Z">BlueKnight</metadata>
</glsa>