blob: 60d507513c382fbb984c5488b46932bed4b339b9 (
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
65
66
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200903-01">
<title>Vinagre: User-assisted execution of arbitrary code</title>
<synopsis>
A format string error in Vinagre may allow for the execution of arbitrary
code.
</synopsis>
<product type="ebuild">vinagre</product>
<announced>March 06, 2009</announced>
<revised>March 06, 2009: 01</revised>
<bug>250314</bug>
<access>remote</access>
<affected>
<package name="net-misc/vinagre" auto="yes" arch="*">
<unaffected range="ge">0.5.2</unaffected>
<vulnerable range="lt">0.5.2</vulnerable>
</package>
</affected>
<background>
<p>
Vinagre is a VNC Client for the GNOME Desktop.
</p>
</background>
<description>
<p>
Alfredo Ortega (Core Security Technologies) reported a format string
error in the vinagre_utils_show_error() function in
src/vinagre-utils.c.
</p>
</description>
<impact type="normal">
<p>
A remote attacker could entice a user into opening a specially crafted
.vnc file or connecting to a malicious server, possibly resulting in
the remote execution of arbitrary code with the privileges of the user
running the application.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All Vinagre users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-misc/vinagre-0.5.2"</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5660">CVE-2008-5660</uri>
</references>
<metadata tag="requester" timestamp="Sat, 13 Dec 2008 19:36:32 +0000">
keytoaster
</metadata>
<metadata tag="submitter" timestamp="Tue, 24 Feb 2009 22:12:27 +0000">
p-y
</metadata>
<metadata tag="bugReady" timestamp="Tue, 24 Feb 2009 22:12:38 +0000">
p-y
</metadata>
</glsa>
|