A security issue and some vulnerabilities have been reported in OpenOffice.org, which can be exploited by malicious, local users to gain escalated privileges and by malicious people to compromise a user's system.

1) An integer truncation error when parsing certain content can be exploited to cause a heap-based buffer overflow via a specially crafted file.

2) A short integer overflow error when parsing certain content can be exploited to cause a heap-based buffer overflow via a specially crafted file.

3) A use-after-free error when parsing tables in RTF documents can be exploited to dereference freed memory by e.g. tricking a user into opening an RTF document containing specially crafted table data.

4) A signedness error when parsing the "\pnseclvl" RTF tag can be exploited to dereference freed memory by e.g. tricking a user into opening a specially crafted RTF document.

5) An array indexing error when parsing list data in Word documents can be exploited to corrupt memory by e.g. tricking a user into opening a specially crafted Word document.

6) Two input sanitisation errors when parsing Word documents can be exploited to write two NULL bytes into arbitrary memory locations.

7) A security issue is caused due to certain shell scripts incorrectly setting the environment variable LD_LIBRARY_PATH. This can be exploited to gain escalated privileges e.g. by tricking a user into running the script in a directory containing a malicious library.

8) Two vulnerabilities are caused due to the use of vulnerable libxml2 code.

For more information:
SA42175
SA42721

Note: It's currently unknown, whether or not OpenOffice.org uses the vulnerable code parts.

9) An unspecified error within the processing of PNG images can be exploited to execute arbitrary code by e.g. tricking a user into opening specially crafted ODF and MS Office documents.

10) An unspecified error within the processing of TGA images can be exploited to execute arbitrary code by e.g. tricking a user into opening specially crafted ODF and MS Office documents.

11) An input validation error when extracting ZIP or JAR archives can be exploited to extract files into arbitrary locations outside of the destination folder via directory traversal attacks.

Solution
Update to version 3.3.

Provided and/or discovered by
1,2) Charlie Miller, Independent Security Evaluators.
3,4,5,6) Dan Rosenberg, Virtual Security Research

The vendor credits:
7) Dmitri Gribenko
9, 11) Marc Schoenefeld, Red Hat Security Response Team
10) babi via Beyond Security's SecuriTeam Secure Disclosure program

Changelog
Further details available to Secunia VIM customers

Original Advisory
OpenOffice.org:
1,2) http://www.openoffice.org/security/cves/CVE-2010-2935_CVE-2010-2936.html
3,4) http://www.openoffice.org/security/cves/CVE-2010-3451_CVE-2010-3452.html
5,6) http://www.openoffice.org/security/cves/CVE-2010-3453_CVE-2010-3454.html
7) http://www.openoffice.org/security/cves/CVE-2010-3689.html
8) http://www.openoffice.org/security/cves/CVE-2010-4008_CVE-2010-4494.html
9) http://www.openoffice.org/security/cves/CVE-2010-4253.html
10) http://www.openoffice.org/security/cves/CVE-2010-4643.html
11) http://www.openoffice.org/security/cves/CVE-2010-3450.html

Virtual Security Research:
http://www.vsecurity.com/resources/advisory/20110126-1/

Charlie Miller, "Crash analysis with BitBlaze (page 58 - 65)":
http://securityevaluators.com/files/papers/CrashAnalysis.pdf

Other references
Further details available to Secunia VIM customers

Deep Links
Links available to Secunia VIM customers