summaryrefslogtreecommitdiff
blob: 7547f6b6023a2677a1989208c16b7d3a7cf08209 (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
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200904-03">
  <title>Gnumeric: Untrusted search path</title>
  <synopsis>
    An untrusted search path vulnerability in Gnumeric might result in the
    execution of arbitrary code.
  </synopsis>
  <product type="ebuild">gnumeric</product>
  <announced>2009-04-03</announced>
  <revised>2009-04-03: 01</revised>
  <bug>257012</bug>
  <access>local</access>
  <affected>
    <package name="app-office/gnumeric" auto="yes" arch="*">
      <unaffected range="ge">1.8.4-r1</unaffected>
      <vulnerable range="lt">1.8.4-r1</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    The Gnumeric spreadsheet is a versatile application developed as part
    of the GNOME Office project.
    </p>
  </background>
  <description>
    <p>
    James Vega reported an untrusted search path vulnerability in the
    GObject Python interpreter wrapper in Gnumeric.
    </p>
  </description>
  <impact type="normal">
    <p>
    A local attacker could entice a user to run Gnumeric from a directory
    containing a specially crafted python module, resulting in the
    execution of arbitrary code with the privileges of the user running
    Gnumeric.
    </p>
  </impact>
  <workaround>
    <p>
    Do not run "gnumeric" from untrusted working directories.
    </p>
  </workaround>
  <resolution>
    <p>
    All Gnumeric users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=app-office/gnumeric-1.8.4-r1"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0318">CVE-2009-0318</uri>
  </references>
  <metadata tag="submitter" timestamp="2009-04-02T12:39:58Z">
    rbu
  </metadata>
  <metadata tag="bugReady" timestamp="2009-04-02T12:40:05Z">
    rbu
  </metadata>
</glsa>