blob: fea5db6ea3b2168b2f0413bdcc5b8e9e844bd4d4 (
plain)
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
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201205-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-05-15</announced>
<revised count="1">2012-05-15</revised>
<bug>414199</bug>
<access>remote</access>
<affected>
<package name="www-client/chromium" auto="yes" arch="*">
<unaffected range="ge">18.0.1025.168</unaffected>
<vulnerable range="lt">18.0.1025.168</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, or a Denial of Service
condition.
</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
">=www-client/chromium-18.0.1025.168"
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3078">CVE-2011-3078</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3081">CVE-2011-3081</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-1521">CVE-2012-1521</uri>
<uri link="https://googlechromereleases.blogspot.com/2012/04/stable-channel-update_30.html">
Release Notes 18.0.1025.168
</uri>
</references>
<metadata timestamp="2012-05-02T15:49:58Z" tag="requester">
phajdan.jr
</metadata>
<metadata timestamp="2012-05-15T06:57:17Z" tag="submitter">
phajdan.jr
</metadata>
</glsa>
|