blob: 0484ae60b7c113ce72f0a0808253d00a1e8b5569 (
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="200902-03">
<title>Valgrind: Untrusted search path</title>
<synopsis>
An untrusted search path vulnerability in Valgrind might result in the
execution of arbitrary code.
</synopsis>
<product type="ebuild">valgrind</product>
<announced>2009-02-12</announced>
<revised count="01">2009-02-12</revised>
<bug>245317</bug>
<access>local</access>
<affected>
<package name="dev-util/valgrind" auto="yes" arch="*">
<unaffected range="ge">3.4.0</unaffected>
<vulnerable range="lt">3.4.0</vulnerable>
</package>
</affected>
<background>
<p>
Valgrind is an open-source memory debugger.
</p>
</background>
<description>
<p>
Tavis Ormandy reported that Valgrind loads a .valgrindrc file in the
current working directory, executing commands specified there.
</p>
</description>
<impact type="high">
<p>
A local attacker could prepare a specially crafted .valgrindrc file and
entice a user to run Valgrind from the directory containing that file,
resulting in the execution of arbitrary code with the privileges of the
user running Valgrind.
</p>
</impact>
<workaround>
<p>
Do not run "valgrind" from untrusted working directories.
</p>
</workaround>
<resolution>
<p>
All Valgrind users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-util/valgrind-3.4.0"</code>
</resolution>
<references>
<uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4865">CVE-2008-4865</uri>
</references>
<metadata tag="requester" timestamp="2009-01-13T17:33:22Z">
rbu
</metadata>
<metadata tag="submitter" timestamp="2009-01-13T17:46:15Z">
rbu
</metadata>
<metadata tag="bugReady" timestamp="2009-01-13T17:47:39Z">
rbu
</metadata>
</glsa>
|
GitWeb
