Home / vulnerabilities 04.17.08-1.txt
Posted on 18 April 2008
Source : packetstormsecurity.org Link
iDefense Security Advisory 04.17.08
http://labs.idefense.com/intelligence/vulnerabilities/
Apr 17, 2008
I. BACKGROUND
OpenOffice is an open-source desktop office suite for many of today's
popular operating systems. Object Linking and Embedding (OLE) is a
proprietary binary file format developed by Microsoft. OLE is used for
Office files such as PowerPoint (PPT), Excel (XLS), and Word (DOC).
More information is available from the following URL.
http://www.openoffice.org/
II. DESCRIPTION
Remote exploitation of a heap based buffer overflow vulnerability in
OpenOffice.org's OpenOffice, as included in various vendors' operating
system distributions, could allow an attacker to execute arbitrary code
with the privileges of the current user.
The vulnerability exists within the importer for files stored using the
OLE format. When parsing the "DocumentSummaryInformation" stream, the
vulnerable code does not correctly verify the size of a destination
buffer before copying data from the file into it. This results in an
exploitable heap overflow.
III. ANALYSIS
Exploitation of this vulnerability results in the execution of arbitrary
code with the privileges of the user opening the file. To exploit this
vulnerability, an attacker must persuade a user to open a malicious
file.
IV. DETECTION
iDefense confirmed the existence of this vulnerability in OpenOffice
version 2.3.1. Other versions may also be affected.
V. WORKAROUND
iDefense is currently unaware of any workarounds for this issue.
VI. VENDOR RESPONSE
The OpenOffice.org team has addressed this vulnerability with the
release of version 2.4. For more information, consult the OOo Security
Bulletin at the following URL.
http://www.openoffice.org/security/cves/CVE-2008-0320.html
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2008-0320 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
security problems.
VIII. DISCLOSURE TIMELINE
01/08/2008 Initial vendor response
01/08/2008 Initial vendor notification
04/17/2008 Coordinated public disclosure
IX. CREDIT
This vulnerability was reported to iDefense by Marsu.
Get paid for vulnerability research
http://labs.idefense.com/methodology/vulnerability/vcp.php
Free tools, research and upcoming events
http://labs.idefense.com/
X. LEGAL NOTICES
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically,
please e-mail customerservice@idefense.com for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct,
indirect, or consequential loss or damage arising from use of, or
reliance on, this information.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
