glsa-201202-01.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
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201202-01">
  <title>Chromium: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been reported in Chromium, some of
    which may allow execution of arbitrary code.
  </synopsis>
  <product type="ebuild">chromium</product>
  <announced>2012-02-18</announced>
  <revised count="1">2012-02-18</revised>
  <bug>402841</bug>
  <bug>404067</bug>
  <access>remote</access>
  <affected>
    <package name="www-client/chromium" auto="yes" arch="*">
      <unaffected range="ge">17.0.963.56</unaffected>
      <vulnerable range="lt">17.0.963.56</vulnerable>
    </package>
  </affected>
  <background>
    <p>Chromium is an open source web browser project.</p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in Chromium. Please review
      the CVE identifiers and release notes referenced below for details.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could entice a user to open a specially crafted web
      site using Chromium, possibly resulting in the execution of arbitrary
      code with the privileges of the process, a Denial of Service condition,
      information leak (clipboard contents), bypass of the Same Origin Policy,
      or escape from NativeClient's sandbox.
    </p>
    
    <p>A remote attacker could also entice the user to perform a set of UI
      actions (drag and drop) to trigger an URL bar spoofing vulnerability.
    </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-17.0.963.56"
    </code>
  </resolution>
  <references>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3016">
      CVE-2011-3016
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3017">
      CVE-2011-3017
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3018">
      CVE-2011-3018
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3019">
      CVE-2011-3019
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3020">
      CVE-2011-3020
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3021">
      CVE-2011-3021
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3022">
      CVE-2011-3022
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3023">
      CVE-2011-3023
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3024">
      CVE-2011-3024
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3025">
      CVE-2011-3025
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3027">
      CVE-2011-3027
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3953">
      CVE-2011-3953
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3954">
      CVE-2011-3954
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3955">
      CVE-2011-3955
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3956">
      CVE-2011-3956
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3957">
      CVE-2011-3957
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3958">
      CVE-2011-3958
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3959">
      CVE-2011-3959
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3960">
      CVE-2011-3960
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3961">
      CVE-2011-3961
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3962">
      CVE-2011-3962
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3963">
      CVE-2011-3963
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3964">
      CVE-2011-3964
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3965">
      CVE-2011-3965
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3966">
      CVE-2011-3966
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3967">
      CVE-2011-3967
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3968">
      CVE-2011-3968
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3969">
      CVE-2011-3969
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3970">
      CVE-2011-3970
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3971">
      CVE-2011-3971
    </uri>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3972">
      CVE-2011-3972
    </uri>
    <uri link="https://googlechromereleases.blogspot.com/2012/02/stable-channel-update.html">
      Release Notes 17.0.963.46
    </uri>
    <uri link="https://googlechromereleases.blogspot.com/2012/02/chrome-stable-update.html">
      Release Notes 17.0.963.56
    </uri>
  </references>
  <metadata timestamp="2012-02-13T09:29:19Z" tag="requester">
    phajdan.jr
  </metadata>
  <metadata timestamp="2012-02-18T17:34:34Z" tag="submitter">
    phajdan.jr
  </metadata>
</glsa>