blob: 0406eca4ba6bbd0e06caa28d5ee3149f49d9474f (
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
61
62
63
64
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200712-11">
<title>Portage: Information disclosure</title>
<synopsis>
Portage may disclose sensitive information when updating configuration
files.
</synopsis>
<product type="ebuild">portage</product>
<announced>December 13, 2007</announced>
<revised>December 13, 2007: 01</revised>
<bug>193589</bug>
<access>local</access>
<affected>
<package name="sys-apps/portage" auto="yes" arch="*">
<unaffected range="ge">2.1.3.11</unaffected>
<vulnerable range="lt">2.1.3.11</vulnerable>
</package>
</affected>
<background>
<p>
Portage is the default Gentoo package management system.
</p>
</background>
<description>
<p>
Mike Frysinger reported that the "etc-update" utility uses temporary
files with the standard umask, which results in the files being
world-readable when merging configuration files in a default setup.
</p>
</description>
<impact type="normal">
<p>
A local attacker could access sensitive information when configuration
files are being merged.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All Portage users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-apps/portage-2.1.3.11"</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6249">CVE-2007-6249</uri>
</references>
<metadata tag="requester" timestamp="Mon, 10 Dec 2007 21:27:57 +0000">
p-y
</metadata>
<metadata tag="bugReady" timestamp="Mon, 10 Dec 2007 21:28:40 +0000">
p-y
</metadata>
<metadata tag="submitter" timestamp="Tue, 11 Dec 2007 22:39:19 +0000">
p-y
</metadata>
</glsa>
|
GitWeb
