blob: 32c8ce01ec27c390da5c4b1c65a61d8c49d779bc [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head profile="http://www.w3.org/2005/10/profile">
<title>CVE-2008-2152</title>
<style type="text/css">
/*<![CDATA[*/
hr { display: block }
/*]]>*/
</style>
</head>
<body>
<h2><a href=
"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2152">CVE-2008-2152</a></h2>
<h3>Integer Overflow vulnerability in rtl_allocateMemory()</h3>
<ul>
<li><strong>Synopsis:</strong>Different kinds of manipulated files may
lead to heap overflows and arbitrary code execution</li>
<li><strong>State:</strong> Resolved</li>
</ul>
<h4>1. Impact</h4>
<p>A security vulnerability in the custom memory allocation function from
OpenOffice.org may lead to heap overflows and allow a remote unprivileged
user who provides a OpenOffice.org document that is opened by a local user
to execute arbitrary commands on the system with the privileges of the user
running OpenOffice.org. No working exploit is known right now.</p>
<h4>2. Affected releases</h4>
<p>All versions between OpenOffice.org 2.0 and 2.4 inclusive.</p>
<h4>3. Symptoms</h4>
<p>There are no predictable symptoms that would indicate this issue has
occurred</p>
<h4>4. Relief/Workaround</h4>
<p>There is no workaround. See "Resolution" below.</p>
<h4>5. Resolution</h4>
<p>This issue is addressed in the following release:</p>
<p><strong>OpenOffice.org 2.4.1</strong></p>
<hr />
<p><a href="//security/">Security Home</a> -&gt;
<a href="//security/bulletin.html">Bulletin</a>
-&gt; <a href=
"//security/cves/CVE-2008-2152.html">CVE-2008-2152</a></p>
<h4>6. Comments</h4>
<p>OpenOffice.org acknowledges with thanks, an anonymous researcher working
with the <a href="http://labs.idefense.com/vcp/">iDefense VCP</a>.</p>
</body>
</html>