|
|
|
View Notes By
|
|
|
|
Other Documents
|
|
|
|
 |
Vulnerability Note VU#170113
OpenOffice.org may fail to recognize embedded Basic macros
OverviewThe OpenOffice.org team has reported a vulnerability in how the 1.1 and 2.0 versions of OpenOffice.org process basic macros.
I. DescriptionA vulnerability in OpenOffice.org may allow an attacker to inject basic code into documents such that the code will be executed when the document is loaded. After the document is opened, the user will not be alerted that the macro is running.
To exploit this vulnerability, an attacker would need to convince a user to open a document with a specially crafted basic macro inserted. If successful, the attacker could use the macro to access the operating system with the privileges of the user who opened the document.
II. ImpactA malicious basic macro could change, delete, transmit, overwrite, and read data on the affected computer. It may also be possible for an attacker to remotely execute arbitrary code.
III. SolutionUpgrade
See the systems affected section of this document for information about specific vendors. Users who compile OpenOffice.org from source or get their binaries directly from OpenOffice.org are encouraged to upgrade to version 1.1.5 or 2.0.3.
Systems Affected
References
http://secunia.com/advisories/20893/
http://secunia.com/advisories/20867/
http://secunia.com/advisories/20913/
http://secunia.com/advisories/20910/
http://secunia.com/advisories/20975/
http://www.auscert.org.au/6473
http://www.debian.org/security/2006/dsa-1104
http://www.ubuntu.com/usn/usn-313-2
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102490-1
http://www.openoffice.org/security/CVE-2006-2198.html
Credit
This document was written by Ryan Giobbi.
Other Information
| Date Public: | 2006-06-29 |
| Date First Published: | 2006-07-24 |
| Date Last Updated: | 2006-07-24 |
| CERT Advisory: | |
| CVE-ID(s): | CVE-2006-2198 |
| NVD-ID(s): | CVE-2006-2198 |
| US-CERT Technical Alerts: | |
| Metric: | 0.00 |
| Document Revision: | 22 |
If you have feedback, comments, or additional information about this vulnerability, please send us
email.
|
|