blob: 80459b53ec8e3e69de80f829cca8d9b251dcfc50 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200807-05">
<title>OpenOffice.org: User-assisted execution of arbitrary code</title>
<synopsis>
An integer overflow vulnerability has been reported in OpenOffice.org.
</synopsis>
<product type="ebuild">openoffice openoffice-bin</product>
<announced>July 09, 2008</announced>
<revised>July 09, 2008: 01</revised>
<bug>225723</bug>
<access>remote</access>
<affected>
<package name="app-office/openoffice" auto="yes" arch="*">
<unaffected range="ge">2.4.1</unaffected>
<vulnerable range="lt">2.4.1</vulnerable>
</package>
<package name="app-office/openoffice-bin" auto="yes" arch="*">
<unaffected range="ge">2.4.1</unaffected>
<vulnerable range="lt">2.4.1</vulnerable>
</package>
</affected>
<background>
<p>
OpenOffice.org is an open source office productivity suite, including
word processing, spreadsheet, presentation, drawing, data charting,
formula editing, and file conversion facilities.
</p>
</background>
<description>
<p>
Sean Larsson (iDefense Labs) reported an integer overflow in the
function rtl_allocateMemory() in the file
sal/rtl/source/alloc_global.c.
</p>
</description>
<impact type="normal">
<p>
A remote attacker could entice a user to open a specially crafted
document, 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 OpenOffice.org users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=app-office/openoffice-2.4.1&quot;</code>
<p>
All OpenOffice.org binary users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=app-office/openoffice-bin-2.4.1&quot;</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2152">CVE-2008-2152</uri>
</references>
<metadata tag="requester" timestamp="Mon, 07 Jul 2008 07:24:43 +0000">
p-y
</metadata>
<metadata tag="bugReady" timestamp="Mon, 07 Jul 2008 07:24:50 +0000">
p-y
</metadata>
<metadata tag="submitter" timestamp="Mon, 07 Jul 2008 11:42:11 +0000">
p-y
</metadata>
</glsa>