blob: fb22a1dc253305dce67be7bfd6b67bcb33cf10c6 (
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="200802-05">
<title>Gnumeric: User-assisted execution of arbitrary code</title>
<synopsis>
Several integer overflow vulnerabilities have been reported in Gnumeric,
possibly resulting in user-assisted execution of arbitrary code.
</synopsis>
<product type="ebuild">gnumeric</product>
<announced>February 12, 2008</announced>
<revised>February 12, 2008: 01</revised>
<bug>208356</bug>
<access>remote</access>
<affected>
<package name="app-office/gnumeric" auto="yes" arch="*">
<unaffected range="ge">1.8.1</unaffected>
<vulnerable range="lt">1.8.1</vulnerable>
</package>
</affected>
<background>
<p>
The Gnumeric spreadsheet is a versatile application developed as part
of the GNOME Office project.
</p>
</background>
<description>
<p>
Multiple integer overflow and signedness errors have been reported in
the excel_read_HLINK() function in file plugins/excel/ms-excel-read.c
when processing XLS HLINK opcodes.
</p>
</description>
<impact type="normal">
<p>
A remote attacker could entice a user to open a specially crafted XLS
file, 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 Gnumeric users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-office/gnumeric-1.8.1"</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0668">CVE-2008-0668</uri>
</references>
<metadata tag="requester" timestamp="Sun, 10 Feb 2008 23:12:13 +0000">
p-y
</metadata>
<metadata tag="bugReady" timestamp="Sun, 10 Feb 2008 23:12:22 +0000">
p-y
</metadata>
<metadata tag="submitter" timestamp="Tue, 12 Feb 2008 08:14:23 +0000">
p-y
</metadata>
</glsa>
|