You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by wa...@apache.org on 2020/11/02 20:07:52 UTC
[openoffice-org] 02/02: Migration of security html content
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
commit c8486dfaf197d574ddf7eb0dd041cb19fb7169b1
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Mon Nov 2 12:07:45 2020 -0800
Migration of security html content
---
content/security/CVE-2006-2198.html | 49 +++++
content/security/CVE-2006-2199.html | 63 ++++++
content/security/CVE-2006-3117.html | 56 +++++
content/security/about_badbunny_macros.html | 28 +++
content/security/alerts.html | 40 ++++
content/security/bulletin-20060629.html | 23 ++
content/security/bulletin.html | 243 +++++++++++++++++++++
content/security/cves/CVE-2006-2198.html | 49 +++++
content/security/cves/CVE-2006-2199.html | 63 ++++++
content/security/cves/CVE-2006-3117.html | 56 +++++
content/security/cves/CVE-2006-4339.html | 70 ++++++
content/security/cves/CVE-2006-5870.html | 47 ++++
content/security/cves/CVE-2007-0238.html | 42 ++++
content/security/cves/CVE-2007-0239.html | 44 ++++
content/security/cves/CVE-2007-0245.html | 73 +++++++
content/security/cves/CVE-2007-2.html | 43 ++++
content/security/cves/CVE-2007-2754.html | 74 +++++++
content/security/cves/CVE-2007-2834.html | 73 +++++++
content/security/cves/CVE-2007-4575.html | 72 ++++++
content/security/cves/CVE-2007-4770.html | 63 ++++++
content/security/cves/CVE-2007-5745.html | 68 ++++++
content/security/cves/CVE-2007-5746.html | 68 ++++++
content/security/cves/CVE-2008-0320.html | 69 ++++++
content/security/cves/CVE-2008-2152.html | 66 ++++++
content/security/cves/CVE-2008-2237.html | 70 ++++++
content/security/cves/CVE-2008-2238.html | 70 ++++++
content/security/cves/CVE-2009-0200-0201.html | 79 +++++++
content/security/cves/CVE-2009-0217.html | 68 ++++++
content/security/cves/CVE-2009-2414-2416.html | 80 +++++++
content/security/cves/CVE-2009-2493.html | 76 +++++++
content/security/cves/CVE-2009-2949.html | 68 ++++++
content/security/cves/CVE-2009-2950.html | 68 ++++++
content/security/cves/CVE-2009-3301-3302.html | 69 ++++++
content/security/cves/CVE-2009-3555.html | 62 ++++++
content/security/cves/CVE-2010-0395.html | 70 ++++++
.../security/cves/CVE-2010-2935_CVE-2010-2936.html | 59 +++++
content/security/cves/CVE-2010-3450.html | 64 ++++++
.../security/cves/CVE-2010-3451_CVE-2010-3452.html | 63 ++++++
.../security/cves/CVE-2010-3453_CVE-2010-3454.html | 63 ++++++
content/security/cves/CVE-2010-3689.html | 62 ++++++
.../security/cves/CVE-2010-3702_CVE-2010-3704.html | 53 +++++
.../security/cves/CVE-2010-4008_CVE-2010-4494.html | 57 +++++
content/security/cves/CVE-2010-4253.html | 65 ++++++
content/security/cves/CVE-2010-4643.html | 66 ++++++
content/security/cves/CVE-2012-0037.html | 102 +++++++++
content/security/cves/CVE-2012-1149.html | 52 +++++
content/security/cves/CVE-2012-2149.html | 49 +++++
content/security/cves/CVE-2012-2334.html | 44 ++++
content/security/cves/CVE-2012-2665.html | 59 +++++
content/security/cves/CVE-2013-1571.html | 83 +++++++
content/security/cves/CVE-2013-2189.html | 41 ++++
content/security/cves/CVE-2013-4156.html | 41 ++++
content/security/cves/CVE-2014-3524.html | 41 ++++
content/security/cves/CVE-2014-3575.html | 41 ++++
content/security/cves/CVE-2015-1774.html | 103 +++++++++
content/security/cves/CVE-2015-4551.html | 124 +++++++++++
content/security/cves/CVE-2015-5212.html | 109 +++++++++
content/security/cves/CVE-2015-5213.html | 104 +++++++++
content/security/cves/CVE-2015-5214.html | 104 +++++++++
content/security/cves/CVE-2016-1513.html | 163 ++++++++++++++
content/security/cves/CVE-2016-6803.html | 153 +++++++++++++
content/security/cves/CVE-2016-6804.html | 146 +++++++++++++
content/security/cves/CVE-2017-12607.html | 79 +++++++
content/security/cves/CVE-2017-12608.html | 79 +++++++
content/security/cves/CVE-2017-3157.html | 93 ++++++++
content/security/cves/CVE-2017-9806.html | 85 +++++++
content/security/cves/CVE-2018-11790.html | 106 +++++++++
content/security/cves/CVE-2019-9853.html | 129 +++++++++++
content/security/cves/CVE-XXXX-YYYY.html | 123 +++++++++++
content/security/cves/CVE-YYYY-XXXX.html | 63 ++++++
content/security/cves/index.html | 8 +
content/security/faq.html | 192 ++++++++++++++++
content/security/index.html | 67 ++++++
.../response_to_defence_ministry_leak.html | 37 ++++
74 files changed, 5494 insertions(+)
diff --git a/content/security/CVE-2006-2198.html b/content/security/CVE-2006-2198.html
new file mode 100644
index 0000000..8d8aa90
--- /dev/null
+++ b/content/security/CVE-2006-2198.html
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-2198</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+<body>
+<h2>Macro, CVE-2006-2198</h2>
+<h3>Macro Vulnerability</h3>
+<ul>
+ <li> <strong>Synopsis: </strong>Security Vulnerability With Macros in OpenOffice.org
+ <li> <strong>Issue ID: </strong>66863
+ <li> <strong>State: </strong>Resolved
+</ul>
+<h4>1. Impact</h4>
+<p>A security vulnerability in OpenOffice.org may make it possible to inject basic code into documents which is executed upon loading of the document. The user will not be asked or notified and the macro will have full access to system resources with current user's privileges. As a result, the macro may delete/replace files, read/send private data and/or cause additional security issues.</p>
+<p><b>Note:</b> Disabling document macros will not prevent this issue.</p>
+<p>
+This issue is also described in<br>
+CVE-2006-2198, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2198">http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2198</a>,
+<br>
+Sun Alert 102490,
+<a href="http://sunsolve.sun.com/search/document.do?assetkey=1-26-102490-1">
+http://sunsolve.sun.com/search/document.do?assetkey=1-26-102490-1</a>
+</p>
+<h4>2. Contributing Factors</h4>
+<p>This issue can occur in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.x,</strong> <strong>OpenOffice.org 2.0.x</strong></p>
+<h4>3. Symptoms</h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</p>
+<h4>4. Relief/Workaround</h4>
+<p>There is no workaround. Please see the "Resolution" section below.</p>
+<h4>5. Resolution</h4>
+<p>This issue is addressed in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.0.3</strong></p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-2198.html">CVE-2006-2198</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/CVE-2006-2199.html b/content/security/CVE-2006-2199.html
new file mode 100644
index 0000000..afdfe9f
--- /dev/null
+++ b/content/security/CVE-2006-2199.html
@@ -0,0 +1,63 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-2199</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+<h2>Java Applets, CVE-2006-2199</h2>
+<h3>Java Applets </h3>
+<ul><li><strong>Synopsis:</strong> Security Vulnerability With Java Applets in OpenOffice.org </li>
+ <li> <strong>Issue ID:</strong> 66862</li>
+ <li> <strong>State:</strong> Resolved</li>
+</ul>
+<h4><strong>1. Impact</strong></h4>
+<p>A security vulnerability related to OpenOffice.org documents may allow certain Java applets to break through the "sandbox" and therefore have full access to system resources with current user privileges. The offending Applets may be constructed to destroy/replace files, read or send private data, and/or cause additional security issues.</p>
+<p>This issue is also described in
+<br>
+CVE-2006-2199,
+<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2199">http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2199</a>,
+<br>Sun Alert 102475
+<a href="http://sunsolve.sun.com/search/document.do?assetkey=1-26-102475-1">
+http://sunsolve.sun.com/search/document.do?assetkey=1-26-102475-1</a>
+</p>
+<h4><strong>2. Contributing Factors</strong></h4>
+<p>This issue can occur in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.x, OpenOffice.org 2.0.x</strong></p>
+<h4><strong>3. Symptoms</strong></h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</p>
+<h4><strong>4. Relief/Workaround</strong></h4>
+<p>To work around the described issue, disable support for Java Applets (for OpenOffice.org) by doing the following:</p>
+<p><strong>OpenOffice.org 1.x :</strong></p>
+<p>In options dialog: Select --> Tools/Options/OpenOffice.org/Security --> uncheck "Enable Applets"</p>
+<p><strong>OpenOffice.org 2.x </strong></p>
+<p>There is no longer a User Interface (UI) for configuring this option in OpenOffice.org 2.0; the change must be done in configuration files with a text editor. Add the following into your OpenOffice.org settings (typically) for this file <code>"~/.openoffice2.0/user/registry/data/org/openoffice/Office/Common.xcu":</code></p>
+<p><code><node oor:name="Java"><br>
+<node oor:name="Applet"><br>
+<prop oor:name="Enable" oor:type="xs:boolean"><br>
+<value>false</value><br>
+</prop><br>
+</node><br>
+</node></code></p>
+<h4>5. Resolution</h4>
+<p>This issue is addressed in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.0.3</strong></p>
+<p><strong>Notes:</strong></p>
+<p>With the updated versions for OpenOffice.org, support for Java applets in OpenOffice.org will be disabled.</p>
+<p> </p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-2199.html">CVE-2006-2199</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/CVE-2006-3117.html b/content/security/CVE-2006-3117.html
new file mode 100644
index 0000000..18ff24f
--- /dev/null
+++ b/content/security/CVE-2006-3117.html
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-3117</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>File Format, CVE-2006-3117</h2>
+<h3>File Format</h3>
+<ul>
+ <li><strong>Synopsis</strong>: File Format / Buffer Overflow Vulnerability: Loading malformed XML documents can cause buffer overflows and crash OpenOffice.org.</li>
+ <li><strong>Issue ID:</strong> 66866</li>
+ <li><strong>State:</strong> Resolved</li>
+</ul>
+<h4> 1. Impact: </h4>
+<p> The buffer overflow allows for a value to be written to an arbitrary location in memory. This may lead to command execution in the context of the current user. </p>
+<p> This issue is also described in
+<br>
+ CVE-2006-3117 at: <a HREF="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-3117">http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-3117</a>,
+<br>NGSSoftware Advisory,
+<a href="http://www.ngssoftware.com/advisories/openoffice.txt">
+http://www.ngssoftware.com/advisories/openoffice.txt</a>
+<br>
+Sun Alert 102501,
+<a href="http://sunsolve.sun.com/search/document.do?assetkey=1-26-102501-1">
+http://sunsolve.sun.com/search/document.do?assetkey=1-26-102501-1
+</a>
+</p>
+<h4> 2. Contributing Factors: </h4>
+<p> This issue can occur in the following releases:<strong> OpenOffice.org 1.1.x</strong> and <strong>OpenOffice.org 2.0.x</strong> </p>
+<h4> 3. Symptoms: </h4>
+<p> OpenOffice.org can crash due to internal buffer overflows when loading a malformed document. </p>
+<h4> 4. Relief/Workaround:</h4>
+<p> None.</p>
+<h4> 5. Resolution: </h4>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.0.3</strong></p>
+<h4> 6. Credits: </h4>
+<p>
+Wade Alcorn of NGSSoftware discovered the vulnerability and aided in the explanation/fix.
+</P>
+<p> </p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-3117.html">CVE-2006-3117</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/about_badbunny_macros.html b/content/security/about_badbunny_macros.html
new file mode 100644
index 0000000..5b37aec
--- /dev/null
+++ b/content/security/about_badbunny_macros.html
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//SoftQuad Software//DTD HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//EN" "hmpro6.dtd">
+<html><head> <meta http-equiv="content-type" content="text/html; charset=UTF-8">
+
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head>
+
+ <body>
+
+ <h2>About Security, BadBunny, and Macros</h2>
+ <p>23 May 2007</p>
+
+<p> There has been press comment recently about the "SB/BadBunny-A" virus affecting OpenOffice.org reported by an <a href="http://www.sophos.com/security/analyses/sbbadbunnya.html" target="_blank">anti-virus company</a>.</p>
+
+<p> Industry best practice would have been for the anti-virus company to report the virus to the OpenOffice.org security team before making this information public. Unfortunately this did not happen in this case. OpenOffice.org will issue a detailed analysis once a copy of the virus has been received. However, due to the volume of interest in the media, the Community would like to issue the following comments, based on the information available. </p>
+
+<p> Macros are a useful part of any office suite, allowing users to automate repetitive tasks. These tasks include potentially destructive actions such as modifying and deleting files, which is why macros are of interest to virus writers. </p>
+
+<p> It is possible in any capable macro language, including that used by OpenOffice.org, to write simple 'virus-like' programs. Currently, OpenOffice.org follows industry best practice to mitigate the risk. If the software detects macros in a document being opened, by default it displays a warning and will only run the macro if the user specifically agrees. In any macro-capable tool, it is essential to verify the origin and authenticity of the document before executing macros. To this en [...]
+
+<p> The OpenOffice.org engineers take the security of the software very seriously, and will react promptly to any new issues. To do this, they require access to the source code for the alleged virus. From information currently available, it is unlikely that this new virus contains any novel features which would require a software patch. Technically, it is not even a virus, as it is not "self-replicating" - with OpenOffice.org's default settings, it cannot spread without user intervention. </p>
+
+<p>
+However, the OpenOffice.org community repeats the consistent message from
+security experts that users should never accept files from unknown
+sources. For any security issue, please visit OpenOffice.org's <a href="//security/" target="_blank">Security
+Team page</a>.
+</p>
+</body>
+</html>
diff --git a/content/security/alerts.html b/content/security/alerts.html
new file mode 100644
index 0000000..2e74a1e
--- /dev/null
+++ b/content/security/alerts.html
@@ -0,0 +1,40 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+
+ <title>Apache OpenOffice Security Alerts</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2>Apache OpenOffice Security Alerts</h2>
+
+ <p>The Apache OpenOffice Security Team publishes details of security
+ vulnerabilities in our <a href="https://www.openoffice.org/security/bulletin.html">Security
+ Bulletin</a>.</p>
+
+ <p>We also publish these alerts via the project's announcement list, <em>announce</em>.</p>
+
+ <p>If you would like to subscribe to the list, please send a blank email to
+ <a href=
+ "mailto:announce-subscribe@openoffice.apache.org">announce-subscribe@openoffice.apache.org</a>.
+ You will be sent an email from instructions how to confirm your
+ subscription. Once you have confirmed your subscription, you will receive
+ any future emails from announce until you
+ unsubscribe.</p>
+
+ <p>Please note that the mailing list is fully automated, so if you use
+ spam-filtering software, please make sure it will accept emails from
+ <em>announce@openoffice.apache.org</em> <u>before</u> you try and
+ subscribe.</p>
+
+ <a href="https://openoffice.apache.org/security.html">Security Reports</a>
+</body>
+</html>
diff --git a/content/security/bulletin-20060629.html b/content/security/bulletin-20060629.html
new file mode 100644
index 0000000..8d12154
--- /dev/null
+++ b/content/security/bulletin-20060629.html
@@ -0,0 +1,23 @@
+<html>
+
+ <head>
+ <title>
+ Security Bulletin 2006-06-29
+ </title>
+
+</head>
+
+
+<body>
+
+<h2>Security Bulletin 2006-06-29</h2>
+<p>OpenOffice.org 2.0.3 fixes three security vulnerabilites that have been found through internal security audits. Although there are currently no known exploits, we urge all users of 2.0.x prior to 2.0.2 to upgrade to the new version or install their vendor's patches accordingly. Patches for users of OpenOffice.org 1.1.5 will be available shortly.</p>
+<p>The three vulnerabilities involve:</p>
+<ul>
+ <li><a href="CVE-2006-2199.html"> Java Applets, CVE-2006-2199</a></li>
+ <li><a href="CVE-2006-2198.html">Macro, CVE-2006-2198</a>; and</li>
+ <li><a href="CVE-2006-3117.html">File Format, CVE-2006-3117</a></li>
+</ul>
+</body>
+</html>
+
diff --git a/content/security/bulletin.html b/content/security/bulletin.html
new file mode 100644
index 0000000..1a8e6c0
--- /dev/null
+++ b/content/security/bulletin.html
@@ -0,0 +1,243 @@
+<!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>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <title>Apache OpenOffice Security Team Bulletin</title>
+ <style type="text/css">
+ /*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+
+<!-- This page needs further adjustment to avoid style conflicts with
+ the HTML5 wrappers that it is embedded under.
+-->
+
+<h2>Apache OpenOffice Security Team Bulletin</h2>
+
+<p>
+ <strong>
+ If you want to stay up to date on Apache OpenOffice security announcements, please subscribe to our <a href="alerts.html">security-alerts mailing list</a>.
+ </strong>
+</p>
+
+<h3>Fixed in Apache OpenOffice 4.1.7</h3>
+
+<ul>
+ <li><a href="cves/CVE-2019-9853.html">CVE-2019-9853</a>: Insufficient URL decoding flaw in categorizing macro location </li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.1.6</h3>
+
+<ul>
+ <li><a href="cves/CVE-2018-11790.html">CVE-2018-11790</a>: Arithmetic overflow and wrap around during string length calculation </li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.1.5</h3>
+
+<ul>
+ <li>No security vulnerabilities fixed in this release</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.1.4</h3>
+
+<ul>
+ <li><a href="cves/CVE-2017-3157.html">CVE-2017-3157</a>: Arbitrary file disclosure in Calc and Writer</li>
+ <li><a href="cves/CVE-2017-9806.html">CVE-2017-9806</a>: Out-of-Bounds Write in Writer's WW8Fonts Constructor</li>
+ <li><a href="cves/CVE-2017-12607.html">CVE-2017-12607</a>: Out-of-Bounds Write in Impress' PPT Filter</li>
+ <li><a href="cves/CVE-2017-12608.html">CVE-2017-12608</a>: Out-of-Bounds Write in Writer's ImportOldFormatStyles</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.1.3</h3>
+
+<ul>
+ <li><a href="cves/CVE-2016-1513.html">CVE-2016-1513</a>: Memory Corruption Vulnerability (Impress Presentations)</li>
+ <li><a href="cves/CVE-2016-6803.html">CVE-2016-6803</a>: Windows Installer Can Enable Privileged Trojan Execution</li>
+ <li><a href="cves/CVE-2016-6804.html">CVE-2016-6804</a>: Windows Installer Execution of Arbitrary Code with Elevated Privileges</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.1.2</h3>
+
+<ul>
+ <li><a href="cves/CVE-2015-1774.html">CVE-2015-1774</a>: Out-of-Bounds Write in HWP File Filter</li>
+ <li><a href="cves/CVE-2015-4551.html">CVE-2015-4551</a>: Targeted Data Disclosure</li>
+ <li><a href="cves/CVE-2015-5212.html">CVE-2015-5212</a>: ODF Printer Settings Vulnerability</li>
+ <li><a href="cves/CVE-2015-5213.html">CVE-2015-5213</a>: .DOC Document Vulnerability</li>
+ <li><a href="cves/CVE-2015-5214.html">CVE-2015-5214</a>: .DOC Bookmarks Vulnerability</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.1.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2014-3575.html">CVE-2014-3575</a>: Targeted Data Exposure Using Crafted OLE Objects in Apache OpenOffice</li>
+ <li><a href="cves/CVE-2014-3524.html">CVE-2014-3524</a>: Calc Command Injection Vulnerability in Apache OpenOffice</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 4.0.0</h3>
+
+<ul>
+ <li><a href="cves/CVE-2013-2189.html">CVE-2013-2189</a>: DOC Memory Corruption Vulnerability in Apache OpenOffice</li>
+ <li><a href="cves/CVE-2013-4156.html">CVE-2013-4156</a>: DOCM Memory Corruption Vulnerability in Apache OpenOffice</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 3.4.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2012-2665.html">CVE-2012-2665</a>: Manifest-processing errors in Apache OpenOffice 3.4.0</li>
+ <li><a href="cves/CVE-2013-1571.html">CVE-2013-1571</a>: Frame Injection Vulnerability in SDK JavaDoc</li>
+</ul>
+
+<h3>Fixed in Apache OpenOffice 3.4.0</h3>
+
+<ul>
+ <li><a href="cves/CVE-2012-1149.html">CVE-2012-1149</a>: OpenOffice.org integer overflow error in vclmi.dll module when allocating memory for an embedded image object</li>
+ <li><a href="cves/CVE-2012-2149.html">CVE-2012-2149</a>: OpenOffice.org memory overwrite vulnerability</li>
+ <li><a href="cves/CVE-2012-2334.html">CVE-2012-2334</a>: Vulnerabilities related to malformed Powerpoint files in OpenOffice.org 3.3.0</li>
+</ul>
+
+<h3>Patches for OpenOffice.org 3.3</h3>
+
+<ul>
+ <li><a href="cves/CVE-2012-0037.html">CVE-2012-0037</a>: OpenOffice.org data leakage vulnerability</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.3</h3>
+
+<ul>
+ <li><a href="cves/CVE-2010-2935_CVE-2010-2936.html">CVE-2010-2935 / CVE-2010-2936</a>: Security Vulnerability in OpenOffice.org related to PowerPoint document processing</li>
+ <li><a href="cves/CVE-2010-3450.html">CVE-2010-3450</a>: Security Vulnerability in OpenOffice.org related to Extensions and filter package files</li>
+ <li><a href="cves/CVE-2010-3451_CVE-2010-3452.html">CVE-2010-3451 / CVE-2010-3452</a>: Security Vulnerability in OpenOffice.org related to RTF document processing </li>
+ <li><a href="cves/CVE-2010-3453_CVE-2010-3454.html">CVE-2010-3453 / CVE-2010-3454</a>: Security Vulnerability in OpenOffice.org related to Word document processing </li>
+ <li><a href="cves/CVE-2010-3689.html">CVE-2010-3689</a>: Insecure LD_LIBRARY_PATH usage in OpenOffice.org shell scripts </li>
+ <li><a href="cves/CVE-2010-3702_CVE-2010-3704.html">CVE-2010-3702 / CVE-2010-3704</a>: Security Vulnerability in OpenOffice.org's PDF Import extension resulting from 3rd party library XPDF</li>
+ <li><a href="cves/CVE-2010-4008_CVE-2010-4494.html">CVE-2010-4008 / CVE-2010-4494</a>: Possible Security Vulnerability in OpenOffice.org resulting from 3rd party library LIBXML2 </li>
+ <li><a href="cves/CVE-2010-4253.html">CVE-2010-4253</a>: Security Vulnerability in OpenOffice.org related to PNG file processing </li>
+ <li><a href="cves/CVE-2010-4643.html">CVE-2010-4643</a>: Security Vulnerability in OpenOffice.org related to TGA file processing </li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.2.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2009-3555.html">CVE-2009-3555</a>: OpenOffice.org 2 and 3 may be affected by the TLS/SSL Renegotiation Issue in 3rd Party Libraries</li>
+ <li><a href="cves/CVE-2010-0395.html">CVE-2010-0395</a>: Security vulnerability in OpenOffice.org related to python scripting</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.2</h3>
+
+<ul>
+ <li><a href="cves/CVE-2006-4339.html">CVE-2006-4339</a>: Potential vulnerability from 3rd party libxml2 libraries</li>
+ <li><a href="cves/CVE-2009-0217.html">CVE-2009-0217</a>: Potential vulnerability from 3rd party libxmlsec libraries</li>
+ <li><a href="cves/CVE-2009-2493.html">CVE-2009-2493</a>: OpenOffice.org 3 for Windows bundles a vulnerable version of MSVC Runtime</li>
+ <li><a href="cves/CVE-2009-2949.html">CVE-2009-2949</a>: Potential vulnerability related to XPM file processing</li>
+ <li><a href="cves/CVE-2009-2950.html">CVE-2009-2950</a>: Potential vulnerability related to GIF file processing</li>
+ <li><a href="cves/CVE-2009-3301-3302.html">CVE-2009-3301/2</a>: Potential vulnerability related to MS-Word document processing</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.1.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2009-0200-0201.html">CVE-2009-0200 / CVE-2009-0201</a>: Manipulated Microsoft Word files can lead to heap overflows and arbitrary code execution</li>
+ <li><a href="cves/CVE-2009-2414-2416.html">CVE-2009-2414 / CVE-2009-2416</a>: Manipulated XML documents can lead to arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.1</h3>
+
+<ul>
+ <li>No security vulnerabilities fixed in this release</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.0.1</h3>
+
+<ul>
+ <li>No security vulnerabilities fixed in this release</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 3.0</h3>
+
+<ul>
+ <li>No security vulnerabilities fixed in this release</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.4.3</h3>
+
+<ul>
+ <li><a href="cves/CVE-2009-0200-0201.html">CVE-2009-0200 / CVE-2009-0201</a>: Manipulated Microsoft Word files can lead to heap overflows and arbitrary code execution</li>
+ <li><a href="cves/CVE-2009-2414-2416.html">CVE-2009-2414 / CVE-2009-2416</a>: Manipulated XML documents can lead to arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.4.2</h3>
+
+<ul>
+ <li><a href="cves/CVE-2008-2237.html">CVE-2008-2237</a>: Manipulated WMF files can lead to heap overflows and arbitrary code execution</li>
+ <li><a href="cves/CVE-2008-2238.html">CVE-2008-2238</a>: Manipulated EMF files can lead to heap overflows and arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.4.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2008-2152.html">CVE-2008-2152</a>: Different kinds of manipulated files may lead to heap overflows and arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.4</h3>
+
+<ul>
+ <li><a href="cves/CVE-2007-4770.html">CVE-2007-4770/4771</a>: Manipulated ODF text documents containing XForms can lead to heap overflows and arbitrary code execution</li>
+ <li><a href="cves/CVE-2007-5745.html">CVE-2007-5745/5747</a>: Manipulated Quattro Pro files can lead to heap overflows and arbitrary code execution</li>
+ <li><a href="cves/CVE-2007-5746.html">CVE-2007-5746</a>: Manipulated EMF files can lead to heap overflows and arbitrary code execution</li>
+ <li><a href="cves/CVE-2008-0320.html">CVE-2008-0320</a>: Manipulated OLE files can lead to heap overflows and arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.3.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2007-4575.html">CVE-2007-4575</a>: Potential arbitrary code execution vulnerability in 3rd party module (HSQLDB)</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.3</h3>
+
+<ul>
+ <li><a href="cves/CVE-2007-2834.html">CVE-2007-2834</a>: Manipulated TIFF files can lead to heap overflows and arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.2.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2007-2754.html">CVE-2007-2754</a>: Integer overflow and heap-based buffer overflow vulnerability in 3rd party module (freetype)</li>
+ <li><a href="cves/CVE-2007-0245.html">CVE-2007-0245</a>: Manipulated RTF files can lead to heap overflows and arbitrary code execution</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.2</h3>
+
+<ul>
+ <li><a href="cves/CVE-2007-0239.html">CVE-2007-0239</a>: URL Handling Security Vulnerability (Linux/Solaris)</li>
+ <li><a href="cves/CVE-2007-0238.html">CVE-2007-0238</a>: StarCalc Vulnerability</li>
+ <li><a href="cves/CVE-2007-2.html">CVE-2007-002</a>: WordPerfect Import Vulnerability</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.1</h3>
+
+<ul>
+ <li><a href="cves/CVE-2006-5870.html">CVE-2006-5870</a>: WMF/EMF Processing Failures</li>
+</ul>
+
+<h3>Fixed in OpenOffice.org 2.0.3</h3>
+
+<ul>
+ <li><a href="cves/CVE-2006-2199.html">CVE-2006-2199</a>: Java Applets</li>
+ <li><a href="cves/CVE-2006-2198.html">CVE-2006-2198</a>: Macro</li>
+ <li><a href="cves/CVE-2006-3117.html">CVE-2006-3117</a>: File Format</li>
+</ul>
+
+<hr />
+
+<p><a href="http://security.openoffice.org/">Security Home</a> ->
+ <a href="http://security.openoffice.org/bulletin.html">Bulletin</a>
+</p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2006-2198.html b/content/security/cves/CVE-2006-2198.html
new file mode 100644
index 0000000..34a6f17
--- /dev/null
+++ b/content/security/cves/CVE-2006-2198.html
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-2198</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+<body>
+<h2>Macro, CVE-2006-2198</h2>
+<h3>Macro Vulnerability</h3>
+<ul>
+ <li> <strong>Synopsis: </strong>Security Vulnerability With Macros in OpenOffice.org
+ <li> <strong>Issue ID: </strong>66863
+ <li> <strong>State: </strong>Resolved
+</ul>
+<h4>1. Impact</h4>
+<p>A security vulnerability in OpenOffice.org may make it possible to inject basic code into documents which is executed upon loading of the document. The user will not be asked or notified and the macro will have full access to system resources with current user's privileges. As a result, the macro may delete/replace files, read/send private data and/or cause additional security issues.</p>
+<p><b>Note:</b> Disabling document macros will not prevent this issue.</p>
+<p>
+This issue is also described in<br>
+CVE-2006-2198, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2198">http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2198</a>,
+<br>
+Sun Alert 102490,
+<a href="http://sunsolve.sun.com/search/document.do?assetkey=1-26-102490-1">
+http://sunsolve.sun.com/search/document.do?assetkey=1-26-102490-1</a>
+</p>
+<h4>2. Contributing Factors</h4>
+<p>This issue can occur in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.x,</strong> <strong>OpenOffice.org 2.0.x</strong></p>
+<h4>3. Symptoms</h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</p>
+<h4>4. Relief/Workaround</h4>
+<p>There is no workaround. Please see the "Resolution" section below.</p>
+<h4>5. Resolution</h4>
+<p>This issue is addressed in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.0.3</strong></p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-2198.html">CVE-2006-2198</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2006-2199.html b/content/security/cves/CVE-2006-2199.html
new file mode 100644
index 0000000..6eca279
--- /dev/null
+++ b/content/security/cves/CVE-2006-2199.html
@@ -0,0 +1,63 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-2199</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+<h2>Java Applets, CVE-2006-2199</h2>
+<h3>Java Applets </h3>
+<ul><li><strong>Synopsis:</strong> Security Vulnerability With Java Applets in OpenOffice.org </li>
+ <li> <strong>Issue ID:</strong> 66862</li>
+ <li> <strong>State:</strong> Resolved</li>
+</ul>
+<h4><strong>1. Impact</strong></h4>
+<p>A security vulnerability related to OpenOffice.org documents may allow certain Java applets to break through the "sandbox" and therefore have full access to system resources with current user privileges. The offending Applets may be constructed to destroy/replace files, read or send private data, and/or cause additional security issues.</p>
+<p>This issue is also described in
+<br>
+CVE-2006-2199,
+<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2199">http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-2199</a>,
+<br>Sun Alert 102475
+<a href="http://sunsolve.sun.com/search/document.do?assetkey=1-26-102475-1">
+http://sunsolve.sun.com/search/document.do?assetkey=1-26-102475-1</a>
+</p>
+<h4><strong>2. Contributing Factors</strong></h4>
+<p>This issue can occur in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.x, OpenOffice.org 2.0.x</strong></p>
+<h4><strong>3. Symptoms</strong></h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</p>
+<h4><strong>4. Relief/Workaround</strong></h4>
+<p>To work around the described issue, disable support for Java Applets (for OpenOffice.org) by doing the following:</p>
+<p><strong>OpenOffice.org 1.x :</strong></p>
+<p>In options dialog: Select --> Tools/Options/OpenOffice.org/Security --> uncheck "Enable Applets"</p>
+<p><strong>OpenOffice.org 2.x </strong></p>
+<p>There is no longer a User Interface (UI) for configuring this option in OpenOffice.org 2.0; the change must be done in configuration files with a text editor. Add the following into your OpenOffice.org settings (typically) for this file <code>"~/.openoffice2.0/user/registry/data/org/openoffice/Office/Common.xcu":</code></p>
+<p><code><node oor:name="Java"><br>
+<node oor:name="Applet"><br>
+<prop oor:name="Enable" oor:type="xs:boolean"><br>
+<value>false</value><br>
+</prop><br>
+</node><br>
+</node></code></p>
+<h4>5. Resolution</h4>
+<p>This issue is addressed in the following releases:</p>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.0.3</strong></p>
+<p><strong>Notes:</strong></p>
+<p>With the updated versions for OpenOffice.org, support for Java applets in OpenOffice.org will be disabled.</p>
+<p> </p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-2199.html">CVE-2006-2199</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2006-3117.html b/content/security/cves/CVE-2006-3117.html
new file mode 100644
index 0000000..fa04dde
--- /dev/null
+++ b/content/security/cves/CVE-2006-3117.html
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-3117</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>File Format, CVE-2006-3117</h2>
+<h3>File Format</h3>
+<ul>
+ <li><strong>Synopsis</strong>: File Format / Buffer Overflow Vulnerability: Loading malformed XML documents can cause buffer overflows and crash OpenOffice.org.</li>
+ <li><strong>Issue ID:</strong> 66866</li>
+ <li><strong>State:</strong> Resolved</li>
+</ul>
+<h4> 1. Impact: </h4>
+<p> The buffer overflow allows for a value to be written to an arbitrary location in memory. This may lead to command execution in the context of the current user. </p>
+<p> This issue is also described in
+<br>
+ CVE-2006-3117 at: <a HREF="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-3117">http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-3117</a>,
+<br>NGSSoftware Advisory,
+<a href="http://www.ngssoftware.com/advisories/openoffice.txt">
+http://www.ngssoftware.com/advisories/openoffice.txt</a>
+<br>
+Sun Alert 102501,
+<a href="http://sunsolve.sun.com/search/document.do?assetkey=1-26-102501-1">
+http://sunsolve.sun.com/search/document.do?assetkey=1-26-102501-1
+</a>
+</p>
+<h4> 2. Contributing Factors: </h4>
+<p> This issue can occur in the following releases:<strong> OpenOffice.org 1.1.x</strong> and <strong>OpenOffice.org 2.0.x</strong> </p>
+<h4> 3. Symptoms: </h4>
+<p> OpenOffice.org can crash due to internal buffer overflows when loading a malformed document. </p>
+<h4> 4. Relief/Workaround:</h4>
+<p> None.</p>
+<h4> 5. Resolution: </h4>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.0.3</strong></p>
+<h4> 6. Credits: </h4>
+<p>
+Wade Alcorn of NGSSoftware discovered the vulnerability and aided in the explanation/fix.
+</P>
+<p> </p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-3117.html">CVE-2006-3117</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2006-4339.html b/content/security/cves/CVE-2006-4339.html
new file mode 100644
index 0000000..c8718b1
--- /dev/null
+++ b/content/security/cves/CVE-2006-4339.html
@@ -0,0 +1,70 @@
+<!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-2006-4339</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-4339">CVE-2006-4339</a></h2>
+
+ <h3>Security Vulnerability in OpenOffice.org resulting from 3rd party
+ libraries</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> OpenOffice.org 2 and 3 might fail to
+ handle signatures properly due to an issue in 3rd party library libxml2.</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>OpenOffice.org 2 and 3 might fail to handle signatures properly due to
+ the use of a 3rd party library known for having the issue described in
+ <a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-4339">CVE-2006-4339</a>.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.2</li>
+
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: OpenOffice.org 1.1 is not impacted by this issue.</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>None.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2</strong></p><!--
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks Sebastian Apelt from <a href=
+ "http://siberas.com/">siberas</a></p>
+-->
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2006-4339.html">CVE-2006-4339</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2006-5870.html b/content/security/cves/CVE-2006-5870.html
new file mode 100644
index 0000000..d95c8c9
--- /dev/null
+++ b/content/security/cves/CVE-2006-5870.html
@@ -0,0 +1,47 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2006-5870</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>CVE-2006-5870</h2>
+<h3>WMF/EMF Processing Failures </h3>
+<ul>
+ <li> <strong>Synopsis: </strong>Security vulnerability with some WMF/EMF files
+ <li> <strong>Issue ID: </strong>70042
+ <li> <strong>State: </strong>Resolved
+</ul>
+<h4>1. Impact</h4>
+<p>A security vulnerability in OpenOffice.org requiring a tricked user to open a special WMF/EMF file may lead to the user's computer being compromised. </p>
+<p>
+This issue is also described in<br>
+CVE-2006-5870, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5870">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5870</a><br>
+US-Cert,
+<a href="http://www.kb.cert.org/vuls/id/220288">
+http://www.kb.cert.org/vuls/id/220288</a></p>
+<h4>2. Affected releases </h4>
+<p>OpenOffice.org 1.1.x, OpenOffice.org 2.0.x</p>
+<h4>3. Symptoms</h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</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 releases:</p>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.1.x</strong></p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2006-5870.html">CVE-2006-5870</a>
+ </p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-0238.html b/content/security/cves/CVE-2007-0238.html
new file mode 100644
index 0000000..7d7634a
--- /dev/null
+++ b/content/security/cves/CVE-2007-0238.html
@@ -0,0 +1,42 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2007-0238</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>CVE-2007-0238</h2>
+<h3>Manipulated StarCalc files can lead to arbitrary code execution </h3>
+<ul>
+ <li> <strong>Synopsis: </strong>The StarCalc parser in all versions prior to 2.2 contains an exploitable stack overlow due to incorrect handling of the "Note" record.
+ <li> <strong>State: </strong>Resolved
+</ul>
+<h4>1. Impact</h4>
+<p>If a user opens an untrusted StarCalc document it can potentially run arbitrary code supplied in the file. </p>
+<p> This issue is also described in<br>
+ CVE-2007-0238, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0238">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0238</a><br>
+</p>
+<h4>2. Affected releases </h4>
+<p>All versions prior to OpenOffice.org 2.2 </p>
+<h4>3. Symptoms</h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</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 releases:</p>
+<p><strong>OpenOffice.org 1.1.5 Patch, OpenOffice.org 2.2</strong></p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-0238.html">CVE-2007-0238</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-0239.html b/content/security/cves/CVE-2007-0239.html
new file mode 100644
index 0000000..69947c4
--- /dev/null
+++ b/content/security/cves/CVE-2007-0239.html
@@ -0,0 +1,44 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2007-0239</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>CVE-2007-0239</h2>
+<h3>URL Handling Security Vulnerability (Linux/Solaris)</h3>
+<ul>
+ <li> <strong>Synopsis: </strong>The OpenOffice.org URL handler could allow command execution using shell metacharacters in Linux and Solaris.
+ <li> <strong>State: </strong>Resolved for Linux.
+</ul>
+<h4>1. Impact</h4>
+<p>If a user running OpenOffice.org from a shell terminal in Linux or Solaris opens an untrusted URL, malicious code could be arbitrarily executed on the user's computer. </p>
+<p> This issue is also described in<br>
+ CVE-2007-0239, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-239">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-239</a><br>
+ Issue ID#: 58013, 72543</p>
+<h4>2. Affected releases </h4>
+<p>All 2.x versions prior to OpenOffice.org 2.2 for Linux and Solaris </p>
+<p>All 1.x versions for Linux and Solaris. </p>
+<h4>3. Symptoms</h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</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 releases:</p>
+<p><strong>OpenOffice.org 1.5 Patch, OpenOffice.org 2.2 for Linux (affected system) </strong></p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-0239.html">CVE-2007-0239</a>
+ </p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-0245.html b/content/security/cves/CVE-2007-0245.html
new file mode 100644
index 0000000..0fd9795
--- /dev/null
+++ b/content/security/cves/CVE-2007-0245.html
@@ -0,0 +1,73 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>
+ CVE-2007-0245
+</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>
+ CVE-2007-0245
+</h2>
+<h3>
+ Manipulated RTF files can lead to heap overflows and arbitrary code execution
+</h3>
+<ul>
+ <li> <strong>Synopsis: </strong>Manipulated RTF files can lead to heap overflows and arbitrary code execution</li>
+ <li> <strong>State: </strong>Resolved</li>
+</ul>
+<h4>
+ 1. Impact
+</h4>
+<p>
+ A security vulnerability with the way OpenOffice.org processes RTF documents may allow arbitrary command
+ execution on the system with the privileges of the user running OpenOffice.org.
+</p>
+<p>
+ We acknowledge, with thanks, John Heasman of <a href="http://www.ngssoftware.com">NGS Software Ltd</a>
+ for bringing this issue to our attention.
+</p>
+<h4>
+ 2. Affected releases
+</h4>
+<p>
+ All versions prior to OpenOffice.org 2.2.1
+</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 releases:
+</p>
+<p>
+ <strong>OpenOffice.org 2.2.1</strong>
+</p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-0245.html">CVE-2007-0245</a>
+ </p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-2.html b/content/security/cves/CVE-2007-2.html
new file mode 100644
index 0000000..5aa1fcf
--- /dev/null
+++ b/content/security/cves/CVE-2007-2.html
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>CVE-2007-2</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>CVE-2007-2</h2>
+<h3>WordPerfect Import Vulnerability </h3>
+<ul>
+ <li> <strong>Synopsis: </strong>Manipulated WordPerfect files can lead to heap overflow and arbitrary code execution in OpenOffice.org 2.0-2.1
+ <li> <strong>State: </strong>Resolved
+</ul>
+<h4>1. Impact</h4>
+<p>If a user opens an untrusted WordPerfect file his or her system may be compromised. </p>
+<p>
+This issue is also described in<br>
+CVE-2007-0238, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2</a><br>
+</p>
+<h4>2. Affected releases </h4>
+<p>All versions in the 2.x line prior to OpenOffice.org 2.2. Versions in the 1.x line are not affected. </p>
+<h4>3. Symptoms</h4>
+<p>There are no predictable symptoms that would indicate the described issue has been exploited.</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 releases:</p>
+<p><strong>OpenOffice.org 2.2</strong></p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-2.html">CVE-2007-2</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-2754.html b/content/security/cves/CVE-2007-2754.html
new file mode 100644
index 0000000..a642708
--- /dev/null
+++ b/content/security/cves/CVE-2007-2754.html
@@ -0,0 +1,74 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>
+ CVE-2007-2754
+</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>
+ CVE-2007-2754
+</h2>
+<h3>
+ Integer overflow and heap-based buffer overflow vulnerability in 3rd party module (freetype)
+</h3>
+<ul>
+ <li><strong>Synopsis:</strong> Integer overflow and heap-based buffer overflow
+ vulnerability in 3rd party module (freetype)
+</li>
+ <li><strong>State:</strong> Resolved</li>
+</ul>
+<h4>
+ 1. Impact
+</h4>
+<p>
+ Opening manipulated documents which trigger an overflow in the freetype library may
+ allow arbitrary command execution on the system with the privileges of the user running OpenOffice.org.
+</p>
+<p>
+ See also <a href="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-2754">CVE-2007-2754</a>
+</p>
+<h4>
+ 2. Affected releases
+</h4>
+<p>
+ All versions prior to OpenOffice.org 2.2.1
+</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 releases:
+</p>
+<p>
+ <strong>OpenOffice.org 2.2.1</strong>
+</p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-2754.html">CVE-2007-2754</a>
+ </p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-2834.html b/content/security/cves/CVE-2007-2834.html
new file mode 100644
index 0000000..7491612
--- /dev/null
+++ b/content/security/cves/CVE-2007-2834.html
@@ -0,0 +1,73 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>
+ CVE-2007-02834
+</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>
+ CVE-2007-02834
+</h2>
+<h3>
+ Manipulated TIFF files can lead to heap overflows and arbitrary code execution
+</h3>
+<ul>
+ <li> <strong>Synopsis: </strong>Manipulated TIFF files can lead to heap overflows and arbitrary code execution</li>
+ <li> <strong>State: </strong>Resolved</li>
+</ul>
+<h4>
+ 1. Impact
+</h4>
+<p>
+ A security vulnerability with the way OpenOffice.org processes TIFF documents may allow arbitrary command
+ execution on the system with the privileges of the user running OpenOffice.org.
+</p>
+<p>
+ We acknowledge, with thanks, an anonymous researcher working with the
+ <a href="http://labs.idefense.com/vcp">iDefense VCP</a>.
+</p>
+<h4>
+ 2. Affected releases
+</h4>
+<p>
+ All versions prior to OpenOffice.org 2.3
+</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 releases:
+</p>
+<p>
+ <strong>OpenOffice.org 2.3</strong>
+</p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-2834.html">CVE-2007-2834</a>
+ </p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-4575.html b/content/security/cves/CVE-2007-4575.html
new file mode 100644
index 0000000..7f239f7
--- /dev/null
+++ b/content/security/cves/CVE-2007-4575.html
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>
+ CVE-2007-4575
+</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+<body>
+<h2>
+ CVE-2007-4575
+</h2>
+<h3>
+ Potential arbitrary code execution vulnerability in 3rd party module (HSQLDB)
+</h3>
+<ul>
+ <li> <strong>Synopsis: </strong>users opening specially crafted database documents
+ may allow attackers to execute arbitrary static Java code</li>
+ <li> <strong>State: </strong>Resolved</li>
+</ul>
+<h4>
+ 1. Impact
+</h4>
+<p>
+A security vulnerability in HSQLDB, the default database engine shipped
+with OpenOffice.org 2 (all versions), may allow attackers to execute
+arbitrary static Java code, by manipulating database documents to be
+opened by a user.
+</p>
+<h4>
+ 2. Affected releases
+</h4>
+<p>
+ All versions prior to OpenOffice.org 2.3.1
+</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 releases:
+</p>
+<p>
+ <strong>HSQLDB 1.8.0.9 / OpenOffice.org 2.3.1</strong>
+</p>
+ <hr />
+ <p>
+ <a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2007-4575.html">CVE-2007-4575</a>
+ </p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-4770.html b/content/security/cves/CVE-2007-4770.html
new file mode 100644
index 0000000..a454945
--- /dev/null
+++ b/content/security/cves/CVE-2007-4770.html
@@ -0,0 +1,63 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+ <title>CVE-2007-4770/4771</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2>CVE-2007-4770/4771</h2>
+
+ <h3>Manipulated ODF text documents containing XForms can lead to heap overflows and arbitrary code execution</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>Manipulated ODF text documents containing
+ XForms can lead to heap overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice.org 2 processes ODF
+ text documents with XForms, using the 3rd party library ICU, may 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 prior to OpenOffice.org 2.4</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</strong></p>
+ <hr>
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2007-4770.html">CVE-2007-4770/4771</a></p>
+
+</body>
+</html>
diff --git a/content/security/cves/CVE-2007-5745.html b/content/security/cves/CVE-2007-5745.html
new file mode 100644
index 0000000..d659765
--- /dev/null
+++ b/content/security/cves/CVE-2007-5745.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+ <title>CVE-2007-5745/5747</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+ <h2>CVE-2007-5745/5747</h2>
+
+ <h3>Quattro Pro files</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>Manipulated Quattro Pro files can lead to
+ heap overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice.org 2 processes Quattro
+ Pro files may 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 prior to OpenOffice.org 2.4</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</strong></p>
+ <hr>
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2007-5745.html">CVE-2007-5745/5747</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>
diff --git a/content/security/cves/CVE-2007-5746.html b/content/security/cves/CVE-2007-5746.html
new file mode 100644
index 0000000..2370d7e
--- /dev/null
+++ b/content/security/cves/CVE-2007-5746.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+ <title>CVE-2007-5746</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+ <h2>CVE-2007-5746</h2>
+
+ <h3>EMF files</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>Manipulated EMF files can lead to heap
+ overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice.org 1.1 and 2 process
+ EMF files may 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 prior to OpenOffice.org 2.4</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</strong></p>
+ <hr>
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2007-5746.html">CVE-2007-5746</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>
diff --git a/content/security/cves/CVE-2008-0320.html b/content/security/cves/CVE-2008-0320.html
new file mode 100644
index 0000000..1b603c1
--- /dev/null
+++ b/content/security/cves/CVE-2008-0320.html
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+ <title>CVE-2008-0320</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+ <h2>CVE-2008-0320</h2>
+
+ <h3>Manipulated OLE files can lead to heap overflows and arbitrary code
+ execution</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>Manipulated OLE files can lead to heap
+ overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice.org 1.1 and 2 process
+ OLE files may 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 prior to OpenOffice.org 2.4</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</strong></p>
+ <hr>
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2008-0320.html">CVE-2008-0320</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>
diff --git a/content/security/cves/CVE-2008-2152.html b/content/security/cves/CVE-2008-2152.html
new file mode 100644
index 0000000..32c8ce0
--- /dev/null
+++ b/content/security/cves/CVE-2008-2152.html
@@ -0,0 +1,66 @@
+<!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> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <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>
diff --git a/content/security/cves/CVE-2008-2237.html b/content/security/cves/CVE-2008-2237.html
new file mode 100644
index 0000000..c75e3fa
--- /dev/null
+++ b/content/security/cves/CVE-2008-2237.html
@@ -0,0 +1,70 @@
+<!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-2237</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2008-2237">CVE-2008-2237</a></h2>
+
+ <h3>Manipulated WMF files can lead to heap overflows and arbitrary code
+ execution</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>Manipulated WMF files can lead to heap
+ overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice 2.x process WMF files
+ may allow a remote unprivileged user who provides a StarOffice/StarSuite
+ document that is opened by a local user to execute arbitrary commands on
+ the system with the privileges of the user running StarOffice/StarSuite. No
+ working exploit is known right now.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <p>All versions prior to OpenOffice.org 2.4.2</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.2</strong></p>
+
+ <p><em>Note: OpenOffice.org 3.0 is not affected by this
+ vulnerability.</em></p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2008-2237.html">CVE-2008-2237</a></p>
+
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks, an anonymous researcher working
+ with the <a href="http://www.surerun.cn">SureRun Security Team</a>.</p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2008-2238.html b/content/security/cves/CVE-2008-2238.html
new file mode 100644
index 0000000..2108074
--- /dev/null
+++ b/content/security/cves/CVE-2008-2238.html
@@ -0,0 +1,70 @@
+<!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-2238</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2008-2238">CVE-2008-2238</a></h2>
+
+ <h3>Manipulated WMF files can lead to heap overflows and arbitrary code
+ execution</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>Manipulated EMF files can lead to heap
+ overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice 2.x process EMF files
+ may allow a remote unprivileged user who provides a StarOffice/StarSuite
+ document that is opened by a local user to execute arbitrary commands on
+ the system with the privileges of the user running StarOffice/StarSuite. No
+ working exploit is known right now.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <p>All versions prior to OpenOffice.org 2.4.2</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.2</strong></p>
+
+ <p><em>Note: OpenOffice.org 3.0 is not affected by this
+ vulnerability.</em></p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2008-2238.html">CVE-2008-2238</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>
diff --git a/content/security/cves/CVE-2009-0200-0201.html b/content/security/cves/CVE-2009-0200-0201.html
new file mode 100644
index 0000000..690fb2c
--- /dev/null
+++ b/content/security/cves/CVE-2009-0200-0201.html
@@ -0,0 +1,79 @@
+<!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-2009-0200 / CVE-2009-0201</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-0200">CVE-2009-0200</a>
+ / <a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-0201">CVE-2009-0201</a></h2>
+
+ <h3>Manipulated Word documents can lead to heap overflows and arbitrary
+ code execution</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> Manipulated WMF files can lead to heap
+ overflows and arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability with the way OpenOffice.org processes Word
+ documents may allow a remote unprivileged user who provides a Word document
+ that is opened by a local user to execute arbitrary commands on the system
+ with the privileges of the user running OpenOffice.org.<br />
+ No working exploit is known right now.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.1.1</li>
+
+ <li>All versions of OpenOffice.org 2 prior to version 2.4.3</li>
+
+ <li>All versions of OpenOffice.org 1</li>
+ </ul>
+
+ <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 releases:</p>
+
+ <ul>
+ <li><strong>OpenOffice.org 3.1.1</strong></li>
+
+ <li><strong>OpenOffice.org 2.4.3</strong></li>
+ </ul>
+
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks, Dyon Balding of <a href=
+ "http://secunia.com/secunia_research/">Secunia Research</a>.</p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-0200-0201.html">CVE-2009-0200
+ / CVE-2009-0201</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-0217.html b/content/security/cves/CVE-2009-0217.html
new file mode 100644
index 0000000..5d88e2d
--- /dev/null
+++ b/content/security/cves/CVE-2009-0217.html
@@ -0,0 +1,68 @@
+<!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-2009-0217</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-0217">CVE-2009-0217</a></h2>
+
+ <h3>Security Vulnerability in OpenOffice.org resulting from 3rd party
+ library</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> OpenOffice.org 2 and 3 might be affected
+ by XML signature HMAC truncation authentication bypass issue in 3rd party
+ library libxmlsec</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>OpenOffice.org 2 and 3 ship with 3rd party libraries affected by the XML
+ signature HMAC truncation authentication bypass issue documented in
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-0217">CVE-2009-0217</a>.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.2</li>
+
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <h4>3. Symptoms</h4>
+
+ <p>There are no predictable symptoms that would indicate this issue has
+ occurred.</p>
+
+ <h4>4. Relief/Workaround</h4>
+
+ <p>None.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2</strong></p><!--
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks Sebastian Apelt from <a href=
+ "http://siberas.com/">siberas</a></p>
+-->
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-0217.html">CVE-2009-0217</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-2414-2416.html b/content/security/cves/CVE-2009-2414-2416.html
new file mode 100644
index 0000000..89ea0eb
--- /dev/null
+++ b/content/security/cves/CVE-2009-2414-2416.html
@@ -0,0 +1,80 @@
+<!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-2009-2414 / CVE-2009-2416</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2414">CVE-2009-2414</a>
+ / <a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2416">CVE-2009-2416</a></h2>
+
+ <h3>Manipulated XML documents can lead to arbitrary code execution</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> Manipulated XML documents can lead to
+ arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability in OpenOffice.org, related to XML document
+ processing, may allow a remote unprivileged user to execute arbitrary code
+ on the system with the privileges of a local user running OpenOffice.org,
+ if the local user opens crafted XML documents provided by the remote user.
+ These XML documents may also include documents in the OpenDocument format
+ (ODF), the default format used by OpenOffice.org.<br />
+ No working exploit is known right now.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.1.1</li>
+
+ <li>All versions of OpenOffice.org 2 prior to version 2.4.3</li>
+ </ul>
+
+ <p>Note: OpenOffice.org 1 is not impacted by this issue.</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>To workaround the described issues, do not load documents from untrusted
+ sources. See "Resolution" below.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following releases:</p>
+
+ <ul>
+ <li><strong>OpenOffice.org 3.1.1</strong></li>
+
+ <li><strong>OpenOffice.org 2.4.3</strong></li>
+ </ul>
+
+ <h4>6. Comments</h4>
+
+ <p>None</p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-2414-2416.html">CVE-2009-2414
+ / CVE-2009-2416</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-2493.html b/content/security/cves/CVE-2009-2493.html
new file mode 100644
index 0000000..51d7d47
--- /dev/null
+++ b/content/security/cves/CVE-2009-2493.html
@@ -0,0 +1,76 @@
+<!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-2009-2493</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2493">CVE-2009-2493</a></h2>
+
+ <h3>OpenOffice.org 3 for Windows bundles a vulnerable version of MSVC
+ Runtime</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> OpenOffice.org 3 for Windows includes a
+ vulnerable version of the MSVC Runtime, see <a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2493">CVE-2009-2493</a>
+ for details.</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>OpenOffice.org 3 for Windows ships with a vulnerable version of the MSVC
+ Runtime, <a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2493">CVE-2009-2493</a>
+ for details. OpenOffice.org is not affected by the security issue, but
+ centrally installs the vulnerable MSVC Runtime if it didn't exist on the
+ system before. The vulnerable version should be updated automatically by
+ the monthly Windows updates, but newer versions of OpenOffice.org also come
+ with the updated MSVC Runtime.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 for Windows prior to version
+ 3.2</li>
+ </ul>
+
+ <p>Note: OpenOffice.org 2 and OpenOffice.org 1.1 are not impacted by this
+ issue.</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>None.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2</strong></p><!--
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks Sebastian Apelt from <a href=
+ "http://siberas.com/">siberas</a></p>
+-->
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-2493.html">CVE-2009-2493</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-2949.html b/content/security/cves/CVE-2009-2949.html
new file mode 100644
index 0000000..d6f3f36
--- /dev/null
+++ b/content/security/cves/CVE-2009-2949.html
@@ -0,0 +1,68 @@
+<!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-2009-2949</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2949">CVE-2009-2949</a></h2>
+
+ <h3>Security Vulnerability in OpenOffice.org related to XPM file
+ processing</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> Security Vulnerability in OpenOffice.org
+ related to XPM file processing may lead to arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability in OpenOffice.org, related to XPM file
+ processing, may allow a remote unprivileged user to execute arbitrary code
+ on the system with the privileges of a local user running OpenOffice.org,
+ if the local user opens a crafted XPM file provided by the remote user. XPM
+ files can also be embedded in different kind of documents, including
+ documents in the OpenDocument Format (ODF), the default format used by
+ OpenOffice.org.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <p>All versions of OpenOffice.org prior to version 3.2</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>To workaround the described issue, do not load documents from untrusted
+ sources.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks Sebastian Apelt from <a href=
+ "http://siberas.com/">siberas</a></p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-2949.html">CVE-2009-2949</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-2950.html b/content/security/cves/CVE-2009-2950.html
new file mode 100644
index 0000000..06a2e9c
--- /dev/null
+++ b/content/security/cves/CVE-2009-2950.html
@@ -0,0 +1,68 @@
+<!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-2009-2950</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-2950">CVE-2009-2950</a></h2>
+
+ <h3>Security Vulnerability in OpenOffice.org related to GIF file
+ processing</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> Security Vulnerability in OpenOffice.org
+ related to GIF file processing may lead to arbitrary code execution</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability in OpenOffice.org, related to GIF file
+ processing, may allow a remote unprivileged user to execute arbitrary code
+ on the system with the privileges of a local user running OpenOffice.org,
+ if the local user opens a crafted GIF file provided by the remote user. GIF
+ files can also be embedded in different kind of documents, including
+ documents in the OpenDocument Format (ODF), the default format used by
+ OpenOffice.org.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <p>All versions of OpenOffice.org prior to version 3.2</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>To workaround the described issue, do not load documents from untrusted
+ sources.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks, Frank Reißner and Sebastian
+ Apelt from <a href="http://siberas.com/">siberas</a></p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-2950.html">CVE-2009-2950</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-3301-3302.html b/content/security/cves/CVE-2009-3301-3302.html
new file mode 100644
index 0000000..8651828
--- /dev/null
+++ b/content/security/cves/CVE-2009-3301-3302.html
@@ -0,0 +1,69 @@
+<!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-2009-3301/2</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-3301">CVE-2009-3301</a>
+ <a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-3302">CVE-2009-3302</a></h2>
+
+ <h3>Security Vulnerability in OpenOffice.org related to MS-Word document
+ processing</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> A security vulnerability in
+ OpenOffice.org, related to MS-Word document processing, may lead to
+ arbitrary code execution.</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability in OpenOffice.org, related to Word document
+ processing, may allow a remote unprivileged user to execute arbitrary code
+ on the system with the privileges of a local user running OpenOffice.org,
+ if the local user opens a crafted Word document provided by the remote
+ user.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <p>All versions of OpenOffice.org prior to version 3.2</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>To workaround the described issue, do not load documents from untrusted
+ sources.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks, Nicolas Joly of <a href=
+ "http://www.vupen.com/">VUPEN Vulnerability Research Team</a>.</p>
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-3301-3302.html">CVE-2009-3301/2</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2009-3555.html b/content/security/cves/CVE-2009-3555.html
new file mode 100644
index 0000000..9e3c6c3
--- /dev/null
+++ b/content/security/cves/CVE-2009-3555.html
@@ -0,0 +1,62 @@
+<!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-2009-3555</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-3555">CVE-2009-3555</a></h2>
+
+ <h3>OpenOffice.org 2 and 3 may be affected by the TLS/SSL Renegotiation Issue in 3rd Party Libraries</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> OpenOffice.org 2 and 3 may be affected
+ by the TLS/SSL Renegotiation Issue in 3rd Party Libraries.</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>OpenOffice.org 2 and 3 ship with 3rd party libraries affected
+ by the TLS/SSL renegotiation issue documented in CVE-2009-3555.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org prior to version 3.2.1</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: OpenOffice.org 1.1 is not impacted by this issue.</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>None.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2.1</strong></p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2009-3555.html">CVE-2009-3555</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-0395.html b/content/security/cves/CVE-2010-0395.html
new file mode 100644
index 0000000..9b3a9ba
--- /dev/null
+++ b/content/security/cves/CVE-2010-0395.html
@@ -0,0 +1,70 @@
+<!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-2010-0395</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <h2><a href=
+ "http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-0395">CVE-2010-0395</a></h2>
+
+ <h3>Security vulnerability in OpenOffice.org related to python scripting</h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong> A security vulnerability in
+ OpenOffice.org, related to python scripting, may lead to
+ unexpected code execution.</li>
+
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>A security vulnerability in OpenOffice.org, related to python scripting,
+ might lead to unexpected code execution when using the built-in scripting IDE
+ for exploring the python code.</p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org prior to version 3.2.1</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported
+ and will not be evaluated regarding this issue.</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>As a workaround, do not inspect python code from non-trustworthy documents
+ with the built-in scripting IDE and its dialogs.</p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org
+ 3.2.1</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>OpenOffice.org acknowledges with thanks, Marc Schoenefeld from Red Hat Security Response Team.</p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> ->
+ <a href="//security/bulletin.html">Bulletin</a>
+ -> <a href=
+ "//security/cves/CVE-2010-0395.html">CVE-2010-0395</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-2935_CVE-2010-2936.html b/content/security/cves/CVE-2010-2935_CVE-2010-2936.html
new file mode 100755
index 0000000..9537ac1
--- /dev/null
+++ b/content/security/cves/CVE-2010-2935_CVE-2010-2936.html
@@ -0,0 +1,59 @@
+<!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-2010-2935</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2935">CVE-2010-2935</a> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2936">CVE-2010-2936</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org related to PowerPoint document processing
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A security vulnerability in OpenOffice.org, related to PowerPoint document processing, may lead to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A security vulnerability in OpenOffice.org, related to PowerPoint document processing, may allow a remote unprivileged user to execute arbitrary code on the system with the privileges of a local user running OpenOffice.org, if the local user opens a crafted PowerPoint document provided by the remote user.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, do not load documents from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-2935_CVE-2010-2936.html">CVE-2010-2935_CVE-2010-2936</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-3450.html b/content/security/cves/CVE-2010-3450.html
new file mode 100755
index 0000000..d511237
--- /dev/null
+++ b/content/security/cves/CVE-2010-3450.html
@@ -0,0 +1,64 @@
+<!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-2010-3450</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3450">CVE-2010-3450</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org related to Extensions and filter package files
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A directory traversal vulnerability in OpenOffice.org, related to zip/jar package extraction, may lead to overwriting files and even to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A directory traversal vulnerability in OpenOffice.org, related to zip/jar package extraction, may lead to overwriting files when relative file locations point to locations outside the root of the destination folder. This way important files could be overwritten, including executables.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, do not load extensions or filter package files from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ OpenOffice.org acknowledges with thanks, Marc Schoenefeld from Red Hat Security Response Team.
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-3450.html">CVE-2010-3450</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-3451_CVE-2010-3452.html b/content/security/cves/CVE-2010-3451_CVE-2010-3452.html
new file mode 100755
index 0000000..b8b0a40
--- /dev/null
+++ b/content/security/cves/CVE-2010-3451_CVE-2010-3452.html
@@ -0,0 +1,63 @@
+<!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-2010-3451</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3451">CVE-2010-3451</a> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3452">CVE-2010-3452</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org related to RTF document processing
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A security vulnerability in OpenOffice.org, related to RTF document processing, may lead to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A security vulnerability in OpenOffice.org, related to RTF document processing, may allow a remote unprivileged user to execute arbitrary code on the system with the privileges of a local user running OpenOffice.org, if the local user opens a crafted RTF document provided by the remote user.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, do not load documents from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ OpenOffice.org acknowledges with thanks, Dan Rosenberg of Virtual Security Research.
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-3451_CVE-2010-3452.html">CVE-2010-3451_CVE-2010-3452</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-3453_CVE-2010-3454.html b/content/security/cves/CVE-2010-3453_CVE-2010-3454.html
new file mode 100755
index 0000000..8af9d3e
--- /dev/null
+++ b/content/security/cves/CVE-2010-3453_CVE-2010-3454.html
@@ -0,0 +1,63 @@
+<!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-2010-3453</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3453">CVE-2010-3453</a> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3454">CVE-2010-3454</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org related to Word document processing
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A security vulnerability in OpenOffice.org, related to Word document processing, may lead to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A security vulnerability in OpenOffice.org, related to Word document processing, may allow a remote unprivileged user to execute arbitrary code on the system with the privileges of a local user running OpenOffice.org, if the local user opens a crafted Word document provided by the remote user.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, do not load documents from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ OpenOffice.org acknowledges with thanks, Dan Rosenberg of Virtual Security Research.
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-3453_CVE-2010-3454.html">CVE-2010-3453_CVE-2010-3454</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-3689.html b/content/security/cves/CVE-2010-3689.html
new file mode 100755
index 0000000..af042d6
--- /dev/null
+++ b/content/security/cves/CVE-2010-3689.html
@@ -0,0 +1,62 @@
+<!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-2010-3689</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3689">CVE-2010-3689</a></h2>
+
+ <h3>
+ Insecure LD_LIBRARY_PATH usage in OpenOffice.org shell scripts
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ The OpenOffice.org start script and other shell scripts expand the LD_LIBRARY_PATH in a insecure way
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ The OpenOffice.org start script and other shell scripts expand the LD_LIBRARY_PATH in a way that the current directory might be searched for libraries before /lib and /usr/lib, which can have security implications.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ </ul>
+
+ <p>Note: OpenOffice.org 2 is not impacted by this issue. Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, make sure that LD_LIBRARY_PATH is not empty before running soffice or other OpenOffice.org shell scripts.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ OpenOffice.org acknowledges with thanks, Dmitri Gribenko.
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-3689.html">CVE-2010-3689</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-3702_CVE-2010-3704.html b/content/security/cves/CVE-2010-3702_CVE-2010-3704.html
new file mode 100755
index 0000000..fd06c6d
--- /dev/null
+++ b/content/security/cves/CVE-2010-3702_CVE-2010-3704.html
@@ -0,0 +1,53 @@
+<!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-2010-3702</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3702">CVE-2010-3702</a> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3704">CVE-2010-3704</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org's PDF Import extension resulting from 3rd party library XPDF
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A security vulnerability in the 3rd party library XPDF, related to PDF document processing, may lead to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A security vulnerability in the 3rd party library XPDF (only used in the PDF import extension), related to PDF document processing, may allow a remote unprivileged user to execute arbitrary code on the system with the privileges of a local user running OpenOffice.org, if the local user opens a crafted PDF document provided by the remote user.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org's PDF Import extension prior to version 1.0.4</li>
+ </ul>
+
+ <h4>3. Symptoms</h4>
+
+ <p>There are no predictable symptoms that would indicate this issue has occurred.</p>
+
+ <h4>4. Relief/Workaround</h4>
+
+ <p>
+ To workaround the described issue, do not load documents from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>PDF Import Extension 1.0.4</strong></p>
+
+ <hr />
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-3702_CVE-2010-3704.html">CVE-2010-3702_CVE-2010-3704</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-4008_CVE-2010-4494.html b/content/security/cves/CVE-2010-4008_CVE-2010-4494.html
new file mode 100755
index 0000000..327d28b
--- /dev/null
+++ b/content/security/cves/CVE-2010-4008_CVE-2010-4494.html
@@ -0,0 +1,57 @@
+<!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-2010-4008</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-4008">CVE-2010-4008</a> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-4494">CVE-2010-4494</a></h2>
+
+ <h3>
+ Possible Security Vulnerability in OpenOffice.org resulting from 3rd party library LIBXML2
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ OpenOffice.org comes with a vulnerable version of 3rd party library LIBXML2
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ OpenOffice.org comes with a vulnerable version of 3rd party library LIBXML2, but it's unclear whether or not OpenOffice.org actually is impacted by these issues.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ None.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-4008_CVE-2010-4494.html">CVE-2010-4008_CVE-2010-4494</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-4253.html b/content/security/cves/CVE-2010-4253.html
new file mode 100755
index 0000000..6108abb
--- /dev/null
+++ b/content/security/cves/CVE-2010-4253.html
@@ -0,0 +1,65 @@
+<!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-2010-4253</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-4253">CVE-2010-4253</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org related to PNG file processing
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A security vulnerability in OpenOffice.org, related to PNG file processing, may lead to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A security vulnerability in OpenOffice.org, related to PNG file processing, may allow a remote unprivileged user to execute arbitrary code on the system with the privileges of a local user running OpenOffice.org, if the local user opens a crafted PNG file provided by the remote user.
+ <br>
+ Note: PNG files could be embedded in many different document types, including all kind of ODF and MS Office documents.
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, do not load documents from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ OpenOffice.org acknowledges with thanks, Marc Schoenefeld from Red Hat Security Response Team.
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-4253.html">CVE-2010-4253</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2010-4643.html b/content/security/cves/CVE-2010-4643.html
new file mode 100755
index 0000000..8f07d5c
--- /dev/null
+++ b/content/security/cves/CVE-2010-4643.html
@@ -0,0 +1,66 @@
+<!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-2010-4643</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-4643">CVE-2010-4643</a></h2>
+
+ <h3>
+ Security Vulnerability in OpenOffice.org related to TGA file processing
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ A security vulnerability in OpenOffice.org, related to TGA file processing, may lead to arbitrary code execution.
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ A security vulnerability in OpenOffice.org, related to TGA file processing, may allow a remote unprivileged user to execute arbitrary code on the system with the privileges of a local user running OpenOffice.org, if the local user opens a crafted TGA file provided by the remote user.
+ <br>
+ Note: TGA files could be embedded in many different document types, including all kind of ODF and MS Office documents.
+
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ To workaround the described issue, do not load documents from untrusted sources.
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ OpenOffice.org acknowledges with thanks, babi working with Beyond Security's SecuriTeam Secure Disclosure program.
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-2010-4643.html">CVE-2010-4643</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2012-0037.html b/content/security/cves/CVE-2012-0037.html
new file mode 100644
index 0000000..47c0b4f
--- /dev/null
+++ b/content/security/cves/CVE-2012-0037.html
@@ -0,0 +1,102 @@
+<!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-2012-0037</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-0037">CVE-2012-0037</a></h2>
+
+ <h3>
+ OpenOffice.org data leakage vulnerability
+ </h3>
+
+ <ul>
+
+ <h4>Severity: Important</h4>
+
+ <h4>Vendor: The Apache Software Foundation</h4>
+
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>OpenOffice.org 3.3 and 3.4 Beta, on all platforms.</li>
+ <li>Earlier versions may be also affected.</li>
+ </ul>
+
+
+<h4>Description:</h4>
+<p>
+Description: An XML External Entity (XXE) attack is possible in the above versions of OpenOffice.org. This vulnerability exploits the way in
+which external entities are processed in certain XML components of ODF documents. By crafting an external entity to refer to other local file system
+resources, an attacker would be able to inject contents of other locally- accessible files into the ODF document, without the user's knowledge or permission. Data leakage then becomes possible when that document is later distributed to other parties.</p>
+
+ <h4>Mitigation</h4>
+ <p>OpenOffice.org 3.3.0 and 3.4 beta users can patch their installation with the following patches. Download, unzip and follow the instructions in the enclosed readme.pdf file.</p>
+
+ <ul>
+ <li><a href="http://archive.apache.org/dist/incubator/ooo/3.3/patches/cve-2012-0037/CVE-2012-0037-win.zip">For Windows installs</a>
+(<a href="http://archive.apache.org/dist/incubator/ooo/3.3/patches/cve-2012-0037/CVE-2012-0037-win.zip.md5">MD5</a>)
+(<a href="http://archive.apache.org/dist/incubator/ooo/3.3/patches/cve-2012-0037/CVE-2012-0037-win.zip.sha1">SHA1</a>)</li>
+
+ <li><a href="http://archive.apache.org/dist/incubator/ooo/3.3/patches/cve-2012-0037/CVE-2012-0037-mac.zip">For MacOS installs</a>
+(<a href="http://archive.apache.org/dist/incubator/ooo/3.3/patches/cve-2012-0037/CVE-2012-0037-mac.zip.md5">MD5</a>)
+(<a href="http://archive.apache.org/dist/incubator/ooo/3.3/patches/cve-2012-0037/CVE-2012-0037-mac.zip.sha1">SHA1</a>)</li></li>
+ <li>Linux and other platforms should consult their distro or OS vendor for patch instructions.</li>
+ </ul>
+
+ <p>This vulnerability is also fixed in Apache OpenOffice 3.4 dev snapshots since March 1st, 2012.</p>
+
+
+<h4>Verifying the Integrity of Downloaded Files</h4>
+
+<p>
+We have provided MD5 and SHA1 hashes of these patches, as well as a detached digital signature, for those who wish to verify the integrity of these files.
+<p>
+The MD5 and SHA1 hashes can be verified using Unix tools like sha1, sha1sum or md5sum.
+<p>
+The PGP signatures can be verified using PGP or GPG. First download the <a href="https://downloads.apache.org/openoffice/KEYS">KEYS</a> file, as well as the asc signature file for the particular patch from above. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures as follows:
+<p>
+<code>
+% pgpk -a KEYS <br>
+% pgpv CVE-2012-0037-{win|mac}.zip.asc <br>
+</code>
+<em>or</em>
+<br>
+<code>
+% pgp -ka KEYS <br>
+% pgp CVE-2012-0037-{win|mac}.zip.asc <br>
+</code>
+<em>or</em>
+<br>
+<code>
+% gpg --import KEYS <br>
+% gpg --verify CVE-2012-0037-{win|mac}.zip.asc <br>
+</code>
+
+
+
+
+ <h4>Source and Building</h4>
+ <p>Information on obtaining the source code for this patch, and for porting it or adapting it to OpenOffice.org
+ derivatives can be found <a href="CVE-2012-0037-src.txt">here</a>.</p>
+
+ <h4>Credit:</h4>
+ <p>
+ The Apache OpenOffice project acknowledges and thanks the discoverer of this issue, Timothy D. Morgan of Virtual Security Research, LLC.
+ </p>
+
+ <h4>Unofficial translations:</h4>
+ <ul>
+ <li><a href="https://www.openoffice.org/it/stampa/comunicati/CVE-2012-0037.html">Italian</a></li>
+ <li><a href="https://www.openoffice.org/fi/tt/CVE-2012-0037.html">Finnish</a></li>
+ </ul>
+
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a> -> <a href="http://security.openoffice.org/bulletin.html">Bulletin</a> ->
+ <a href="http://security.openoffice.org/security/cves/CVE-2012-0037.html">CVE-2012-0037</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2012-1149.html b/content/security/cves/CVE-2012-1149.html
new file mode 100644
index 0000000..0cdf0ef
--- /dev/null
+++ b/content/security/cves/CVE-2012-1149.html
@@ -0,0 +1,52 @@
+<!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-2012-1149</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a
+ href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-1149">CVE-2012-1149</a></h2>
+
+ <h3>
+ OpenOffice.org integer overflow error in vclmi.dll module when allocating
+ memory for an embedded image object
+ </h3>
+
+ <ul>
+
+ <h4>Severity: Important</h4>
+
+ <h4>Vendor: The Apache Software Foundation</h4>
+
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>OpenOffice.org 3.3 and 3.4 Beta, on all platforms.</li>
+ <li>Earlier versions may be also affected.</li>
+ </ul>
+
+
+<h4>Description:</h4>
+<p> The vulnerability is caused due to an integer overflow error in the
+vclmi.dll module when allocating memory for an embedded image object. This can
+be exploited to cause a heap-based buffer overflow via, for example using a
+specially crafted JPEG object within a DOC file.</p>
+
+ <h4>Mitigation</h4>
+ <p>OpenOffice.org 3.3.0 and 3.4 beta users are advised to <a
+ href="http://download.openoffice.org">upgrade to Apache OpenOffice 3.4</a>. Users who are unable to upgrade immediately
+should be cautious when opening untrusted documents.</p>
+
+<h4>Credits</h4>
+
+<p>The Apache OpenOffice Security Team credits Tielei Wang via Secunia SVCRP as
+ the discoverer of this flaw.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a> -> <a href="../bulletin.html">Bulletin</a> ->
+ <a href="CVE-2012-1149.html">CVE-2012-1149</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2012-2149.html b/content/security/cves/CVE-2012-2149.html
new file mode 100644
index 0000000..1f7f571
--- /dev/null
+++ b/content/security/cves/CVE-2012-2149.html
@@ -0,0 +1,49 @@
+<!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-2012-2149</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-2149">CVE-2012-2149</a></h2>
+
+ <h3>
+ OpenOffice.org memory overwrite vulnerability
+ </h3>
+
+ <ul>
+
+ <h4>Severity: Important</h4>
+
+ <h4>Vendor: The Apache Software Foundation</h4>
+
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>OpenOffice.org 3.3 and 3.4 Beta, on all platforms.</li>
+ <li>Earlier versions may be also affected.</li>
+ </ul>
+
+
+<h4>Description:</h4>
+<p>
+Effected versions of OpenOffice.org use a customized libwpd that has a memory overwrite vulnerability that could be exploited by
+a specially crafted Wordperfect WPD-format document, potentially leading to arbitrary-code execution at application user privilege level.</p>
+
+ <h4>Mitigation</h4>
+ <p>OpenOffice.org 3.3.0 and 3.4 beta users are advised to <a
+href="http://download.openoffice.org">upgrade to Apache OpenOffice 3.4</a>, where
+WPD files are ignored. Users who are unable to upgrade immediately should be
+cautious when opening untrusted WPD documents.</p>
+
+<h4>Credits</h4>
+
+<p>The Apache OpenOffice Security Team acknowledges Kestutis Gudinavicius of SEC Consult Unternehmensberatung GmbH as the discoverer of this flaw.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a> -> <a href="../bulletin.html">Bulletin</a> ->
+ <a href="CVE-2012-2149.html">CVE-2012-2149</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2012-2334.html b/content/security/cves/CVE-2012-2334.html
new file mode 100644
index 0000000..bf56fb7
--- /dev/null
+++ b/content/security/cves/CVE-2012-2334.html
@@ -0,0 +1,44 @@
+<!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-2012-2334</title>
+ <style type="text/css">
+ </style>
+</head>
+<body>
+<h2><a
+href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-2334">CVE-2012-2334</a></h2> <h3>Vulnerabilities related to
+malformed Powerpoint files in OpenOffice.org 3.3.0</h3>
+<ul>
+ <h4>Severity: Important</h4> <h4>Vendor: The Apache Software Foundation</h4> <h4>Versions Affected:</h4>
+ <ul>
+ <li>
+ OpenOffice.org 3.3 and 3.4 Beta, on all platforms.
+ </li>
+ <li>
+ Earlier versions may be also affected.
+ </li>
+ </ul>
+ <h4>Description:</h4>
+ <p>
+ A review of the code in filter/source/msfilter msdffimp.cxx revealed some unchecked memory allocations, which could be
+ exploited via malformed Powerpoint graphics records ("escher") to cause bad_alloc exceptions. From this vulnerability a
+ denial of service attack is possible.
+ </p>
+ <h4>Mitigation</h4>
+ <p>
+ OpenOffice.org 3.3.0 and 3.4 beta users are advised to <a
+ href="http://download.openoffice.org">upgrade to Apache OpenOffice 3.4</a>. Users who are unable to upgrade immediately
+ should be cautious when opening untrusted documents.
+ </p>
+ <h4>Credits</h4>
+ <p>
+ The Apache OpenOffice Security Team credits Sven Jacobias as the discoverer
+ of this flaw.
+ </p>
+ <hr />
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a> -> <a href="../bulletin.html">Bulletin</a> -> <a href="CVE-2012-2334.html">CVE-2012-2334</a>
+ </p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2012-2665.html b/content/security/cves/CVE-2012-2665.html
new file mode 100644
index 0000000..cb7b4d8
--- /dev/null
+++ b/content/security/cves/CVE-2012-2665.html
@@ -0,0 +1,59 @@
+<!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-2012-2665</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a
+ href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-2665">CVE-2012-2665</a></h2>
+
+ <h3> Manifest-processing errors in Apache OpenOffice 3.4.0
+ </h3>
+
+ <ul>
+
+ <h4>Severity: Important</h4>
+
+ <h4>Vendor: The Apache Software Foundation</h4>
+
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>Apache OpenOffice 3.4.0, all languages,
+ all platforms.</li>
+ <li>Earlier versions of OpenOffice.org may
+ be also affected.</li>
+ </ul>
+
+
+<h4>Description:</h4>
+<p> Description: When OpenOffice reads an ODF document, it first loads and
+ processes an XML stream within the file called the manifest. Apache
+ OpenOffice 3.4.0 has logic errors that allows a carefully crafted manifest
+ to cause reads and writes beyond allocated buffers.</p>
+ <p>
+ No specific exploit has been demonstrated
+ in this case, though such flaws generally are conducive to exploitation,
+ possibly including denial of service and elevation of privilege.
+ </p>
+
+ <h4>Mitigation</h4>
+ <p>OpenOffice users are advised to <a
+href="https://www.openoffice.org/download">upgrade to Apache OpenOffice
+3.4.1</a>. Users who are unable
+to upgrade immediately should exercise caution when opening untrusted ODF
+documents.</p>
+
+<h4>Credits</h4>
+
+<p>The Apache OpenOffice Security Team acknowledges Timo Warns of PRESENSE
+ Technologies GmbH as the discoverer of these flaws.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a> -> <a href="../bulletin.html">Bulletin</a> ->
+ <a href="CVE-2012-2665.html">CVE-2012-2665</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2013-1571.html b/content/security/cves/CVE-2013-1571.html
new file mode 100644
index 0000000..6d12e10
--- /dev/null
+++ b/content/security/cves/CVE-2013-1571.html
@@ -0,0 +1,83 @@
+<!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-2013-1571</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-1571">CVE-2013-1571</a></h2>
+
+ <h3>
+ Frame Injection Vulnerability in SDK JavaDoc
+ </h3>
+
+ <ul>
+
+ <h4>Severity: Medium</h4>
+
+ <h4>Vendor: The Apache Software Foundation</h4>
+
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>Apache OpenOffice 3.4.1 SDK, on all platforms.</li>
+ <li>Earlier versions may be also affected.</li>
+ </ul>
+
+
+<h4>Description:</h4>
+<p>
+As reported on June 18th there is a <a href="http://www.kb.cert.org/vuls/id/225657">vulnerability in JavaDoc</a> generated by Java 5, Java 6 and Java 7 before update 22. Generated
+ JavaDoc files could be suceptible to HTML frame injection attacks. Our investigation indicated that the UDK 3.2.7 Java API Reference in the Apache OpenOffice SDK contains
+ a vulnerable HTML file.</p>
+
+<p>Note: Ordinary installs of OpenOffice are not impacted by this vulnerability. Only installs of the OpenOffice SDK, typically only installed by software developers writing
+ extensions, are impacted</p>
+
+ <h4>Mitigation</h4>
+ <p>SDK users should update their installations by replacing /docs/java/ref/index.html with this
+ <a href="http://archive.apache.org/dist/incubator/ooo/3.4.1/source/cve-2013-1571.zip">patched version</a>.
+ Download, unzip and follow the instructions in the enclosed README file.</p>
+
+ <p>Users with earlier versions of the SDK (pre 3.4.1) should <a href="http://www.download.openoffice.org/download/other.html#tested-sdk">upgrade to the current version</a> and then apply the patch. Alternative, they can download and run
+ Oracle's <a href="http://www.oracle.com/technetwork/java/javase/downloads/java-doc-updater-tool-1955731.html">Java API Documentation Updater Tool</a> to repair
+ the vulnerabilities in place.</p>
+
+
+<h4>Verifying the Integrity of Downloaded Files</h4>
+
+<p>
+We have provided <a href="http://archive.apache.org/dist/incubator/ooo/3.4.1/source/cve-2013-1571.zip.md5">MD5</a> and <a href="http://archive.apache.org/dist/incubator/ooo/3.4.1/source/cve-2013-1571.zip.sha256">SHA256</a> hashes of these patches,
+ as well as a <a href="http://archive.apache.org/dist/incubator/ooo/3.4.1/source/cve-2013-1571.zip.asc">GPG/PGP detached digital signature</a>, for those who wish to verify the
+ integrity of this file.
+<p>
+The MD5 and SHA256 hashes can be verified using Unix tools like md5sum or sha256sum.
+<p>
+The PGP signatures can be verified using PGP or GPG. First download the <a href="https://downloads.apache.org/openoffice/KEYS">KEYS</a> file, as well as the asc signature file for the particular patch from above. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures as follows:
+<p>
+<code>
+% pgpk -a KEYS <br>
+% pgpv cve-2013-1571.zip.asc <br>
+</code>
+<em>or</em>
+<br>
+<code>
+% pgp -ka KEYS <br>
+% pgp cve-2013-1571.zip.asc <br>
+</code>
+<em>or</em>
+<br>
+<code>
+% gpg --import KEYS <br>
+% gpg --verify cve-2013-1571.zip.asc <br>
+</code>
+
+
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a> -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a> ->
+ <a href="http://security.openoffice.org/security/cves/CVE-2013-1571.html">CVE-2013-1571</a></p>
+</body>
+</html>
diff --git a/content/security/cves/CVE-2013-2189.html b/content/security/cves/CVE-2013-2189.html
new file mode 100644
index 0000000..930a3db
--- /dev/null
+++ b/content/security/cves/CVE-2013-2189.html
@@ -0,0 +1,41 @@
+<!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-2013-2189</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-2189">CVE-2013-2189</a></h2>
+
+ <h3>OpenOffice DOC Memory Corruption Vulnerability</h3>
+
+ <ul>
+ <h4>Severity: Important</h4>
+ <h4>Vendor: The Apache Software Foundation</h4>
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>Apache OpenOffice 3.4.0 to 3.4.1, on all platforms.</li>
+ <li>Earlier versions may be also affected.</li>
+ </ul>
+
+ <h4>Description:</h4>
+ <p>The vulnerability is caused by operating on invalid PLCF (Plex of Character Positions in File) data when parsing a malformed DOC document file.
+ Specially crafted documents can be used for denial-of-service attacks.
+ Further exploits are possible but have not been verified.
+
+ <h4>Mitigation</h4>
+ <p>Apache OpenOffice 3.4 users are advised to <a href="http://download.openoffice.org">upgrade to Apache OpenOffice 4.0</a>.
+ Users who are unable to upgrade immediately should be cautious when opening untrusted documents.
+
+ <h4>Credits</h4>
+ <p>The Apache OpenOffice security team credits Jeremy Brown of Microsoft Vulnerability Research as the discoverer of this flaw.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="http://security.openoffice.org/security/cves/CVE-2013-2189.html">CVE-2013-2189</a></p>
+</body>
+</html>
+
diff --git a/content/security/cves/CVE-2013-4156.html b/content/security/cves/CVE-2013-4156.html
new file mode 100644
index 0000000..f00bb7b
--- /dev/null
+++ b/content/security/cves/CVE-2013-4156.html
@@ -0,0 +1,41 @@
+<!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-2013-4156</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-4156">CVE-2013-4156</a></h2>
+
+ <h3>OpenOffice DOCM Memory Corruption Vulnerability</h3>
+
+ <ul>
+ <h4>Severity: Important</h4>
+ <h4>Vendor: The Apache Software Foundation</h4>
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>Apache OpenOffice 3.4.0 to 3.4.1, on all platforms.</li>
+ <li>Earlier versions may be also affected.</li>
+ </ul>
+
+ <h4>Description:</h4>
+ <p>The vulnerability is caused by mishandling of unknown XML elements when parsing OOXML document files.
+ Specially crafted documents can be used for denial-of-service attacks.
+ Further exploits are possible but have not been verified.
+
+ <h4>Mitigation</h4>
+ <p>Apache OpenOffice 3.4 users are advised to <a href="http://download.openoffice.org">upgrade to Apache OpenOffice 4.0</a>.
+ Users who are unable to upgrade immediately should be cautious when opening untrusted documents.
+
+ <h4>Credits</h4>
+ <p>The Apache OpenOffice security team credits Jeremy Brown of Microsoft Vulnerability Research as the discoverer of this flaw.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="http://security.openoffice.org/security/cves/CVE-2013-4156.html">CVE-2013-4156</a></p>
+</body>
+</html>
+
diff --git a/content/security/cves/CVE-2014-3524.html b/content/security/cves/CVE-2014-3524.html
new file mode 100644
index 0000000..e2a72ac
--- /dev/null
+++ b/content/security/cves/CVE-2014-3524.html
@@ -0,0 +1,41 @@
+<!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-2014-3524</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-3524">CVE-2014-3524</a></h2>
+
+ <h3>OpenOffice Calc Command Injection Vulnerability</h3>
+
+ <ul>
+ <h4>Severity: Important</h4>
+ <h4>Vendor: The Apache Software Foundation</h4>
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>Apache OpenOffice 4.1.0 and older on Windows.</li>
+ <li>OpenOffice.org versions are also affected.</li>
+ </ul>
+
+ <h4>Description:</h4>
+ <p>The vulnerability allows command injection when loading Calc spreadsheets.
+ Specially crafted documents can be used for command-injection attacks.
+ Further exploits are possible but have not been verified.
+
+ <h4>Mitigation</h4>
+ <p>Apache OpenOffice users are advised to <a href="http://download.openoffice.org">upgrade to Apache OpenOffice 4.1.1</a>.
+ Users who are unable to upgrade immediately should be cautious when opening untrusted documents.
+
+ <h4>Credits</h4>
+ <p>The Apache OpenOffice security team credits Rohan Durve and James Kettle of Context Information Security as the discoverer of this flaw.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="http://security.openoffice.org/security/cves/CVE-2014-3524.html">CVE-2014-3524</a></p>
+</body>
+</html>
+
diff --git a/content/security/cves/CVE-2014-3575.html b/content/security/cves/CVE-2014-3575.html
new file mode 100644
index 0000000..1ae272c
--- /dev/null
+++ b/content/security/cves/CVE-2014-3575.html
@@ -0,0 +1,41 @@
+<!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-2014-3575</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-3575">CVE-2014-3575</a></h2>
+
+ <h3>OpenOffice Targeted Data Exposure Using Crafted OLE Objects</h3>
+
+ <ul>
+ <h4>Severity: Important</h4>
+ <h4>Vendor: The Apache Software Foundation</h4>
+ <h4>Versions Affected:</h4>
+ <ul>
+ <li>Apache OpenOffice 4.1.0 and older on Windows.</li>
+ <li>OpenOffice.org versions are also affected.</li>
+ </ul>
+
+ <h4>Description:</h4>
+ <p>The exposure exploits the way OLE previews are generated to embed arbitrary
+ file data into a specially crafted document when it is opened. Data exposure is
+ possible if the updated document is distributed to other parties.
+
+ <h4>Mitigation</h4>
+ <p>Apache OpenOffice users are advised to <a href="http://download.openoffice.org">upgrade to Apache OpenOffice 4.1.1</a>.
+ Users who are unable to upgrade immediately should be cautious when they are asked to "Update Links" for untrusted documents.
+
+ <h4>Credits</h4>
+ <p>The Apache OpenOffice security team credits Open-Xchange for reporting this flaw.</p>
+
+ <hr />
+
+ <p><a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="http://security.openoffice.org/security/cves/CVE-2014-3575.html">CVE-2014-3575</a></p>
+</body>
+</html>
+
diff --git a/content/security/cves/CVE-2015-1774.html b/content/security/cves/CVE-2015-1774.html
new file mode 100644
index 0000000..9ff43c8
--- /dev/null
+++ b/content/security/cves/CVE-2015-1774.html
@@ -0,0 +1,103 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2015-1774</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-1774">CVE-2015-1774</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2015-1774.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="font-size:larger"><strong>Out-of-Bounds Write in HWP File Filter</strong></p>
+
+
+ <p>
+ <strong>Version 2.0</strong>
+ <br />
+ Announced April 27, 2015<br />
+ Updated October 28, 2015</p>
+
+ <p>
+ A vulnerability in OpenOffice's HWP filter allows attackers to craft
+ malicious documents that cause denial of service (memory
+ corruption and application crash) and possible execution of arbitrary
+ code.
+ </p>
+
+ <p>
+ <strong>Severity: Important</strong>
+ </p>
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ <br />
+ All Apache OpenOffice versions 4.1.1 and older are affected.<br />
+ OpenOffice.org versions are also affected.</p>
+
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+ <p>Update to Apache OpenOffice 4.1.2 or a later version.</p>
+ <p>
+ This mitigation drops Apache OpenOffice support for documents
+ created in "Hangul Word Processor" format. The filter is not
+ installed; it will not be used if present.
+ </p>
+ <p>
+ <strong>Workarounds and Document Migration</strong>
+ </p>
+ <p>
+ Users of older HWP-format documents that are already trusted should
+ convert those documents to other formats before removing the filter
+ or upgrading to Apache OpenOffice version 4.1.2.
+ </p>
+ <p>
+ Apache OpenOffice users who do not upgrade can remove the
+ problematic filter themselves. The filter is in the "program"
+ folder of their OpenOffice installation. On <strong>Windows</strong>
+ the filter is named "hwp.dll", on <strong>Mac OS X</strong> it is named
+ "libhwp.dylib" and on <strong>Linux</strong> it is named "libhwp.so".
+ Alternatively the filter can be renamed to anything else (e.g.
+ "hwp_renamed.dll") to disable its use.
+ </p>
+
+
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+
+ <p><strong>Credits</strong></p>
+ <p>Thanks to an anonymous contributor working with VeriSign iDefense Labs.</p>
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2015-1774.html">CVE-2015-1774</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2015-4551.html b/content/security/cves/CVE-2015-4551.html
new file mode 100644
index 0000000..da25c4a
--- /dev/null
+++ b/content/security/cves/CVE-2015-4551.html
@@ -0,0 +1,124 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2015-4551</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-4551">CVE-2015-4551</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2015-4551.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2015-4551:
+ TARGETED DATA DISCLOSURE</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.2</strong></p>
+
+
+ <p>
+ <strong>Version 1.0</strong>
+ <br />
+ Announced November 4, 2015</p>
+
+ <p>
+ A vulnerability in OpenOffice settings of OpenDocument Format
+ files and templates allows silent access to files that are
+ readable from an user account, over-riding the user's default
+ configuration settings. Once these files are imported into a
+ maliciously-crafted document, the data can be silently hidden
+ in the document and possibly exported to an external party
+ without being observed.
+</p>
+
+ <p>
+ <strong>Severity: Important</strong>
+ </p>
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.</p>
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong></p>
+
+ <p>All Apache OpenOffice versions 4.1.1 and older are affected.<br />
+ OpenOffice.org versions are also affected.</p>
+
+ <p><strong>Related</strong>:
+ <a href="https://www.openoffice.org/security/cves/CVE-2014-3575.html">CVE-2014-3575</a>
+ and <a href="https://www.openoffice.org/security/cves/CVE-2012-0037.html">CVE-2012-0037</a></p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+ <p>Apache OpenOffice users are urged to download and install
+ Apache OpenOffice version 4.1.2 or later.</p>
+ <p>
+ Apache OpenOffice 4.1.2 mitigates this vulnerability by ignoring
+ in-document settings that over-ride default behavior when accessing
+ data beyond the document itself. The automatic default behavior
+ is changed to make such access evident to the user, who must then
+ approve the access.
+ </p>
+ <p>
+ <strong>Nature of Attack</strong>
+ </p>
+ <p>
+ This vulnerability requires an exquisitely crafted attack to
+ locate targeted files, silently retrieve them, and then deliver
+ their data in a manner that escapes notice. Knowledge of the
+ user's system and specific configuration is generally required.
+ </p>
+ <p><strong>Precautions</strong></p>
+ <p>
+
+ <p>
+ In addition to keeping Apache OpenOffice updated, users can reduce
+ the threat of this kind of data access from ODF
+ documents. Keep documents and sensitive materials separate from
+ common, predictable locations, including on networks. Require
+ additional access permissions for access to sensitive materials
+ even when operating under the user's normal account.</p>
+
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+ <p><strong>Credits</strong></p>
+ <p>
+ The Apache OpenOffice security team thanks Federico "fox" Scrinzi
+ for reporting the defect and Stephan Bergmann of Red Hat for
+ analysis and a repair solution.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2015-4551.html">CVE-2015-4551</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2015-5212.html b/content/security/cves/CVE-2015-5212.html
new file mode 100644
index 0000000..959b343
--- /dev/null
+++ b/content/security/cves/CVE-2015-5212.html
@@ -0,0 +1,109 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2015-5212</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-5212">CVE-2015-5212</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2015-5212.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2015-5212:
+ ODF PRINTER SETTINGS VULNERABILITY</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.2</strong></p>
+
+
+ <p>
+ <strong>Version 1.0</strong>
+ <br />
+ Announced November 4, 2015</p>
+
+ <p>
+ A crafted ODF document can be used to create a buffer that is
+ too small for the amount of data loaded into it, allowing an
+ attacker to cause denial of service (memory corruption and
+ application crash) and possible execution of arbitrary code.
+ </p>
+
+ <p>
+ <strong>Severity: Important</strong>
+ </p>
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.</p>
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong></p>
+
+ <p>All Apache OpenOffice versions 4.1.1 and older are affected.<br />
+ OpenOffice.org versions are also affected.</p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+ <p>Apache OpenOffice users are urged to download and install
+ Apache OpenOffice version 4.1.2 or later. Use of in-document
+ control of printer settings is disabled in 4.1.2.</p>
+ <p>
+
+ </p>
+ <p>
+ <strong>Precautions</strong>
+ </p>
+ <p>
+ Users who do not upgrade to Apache OpenOffice 4.1.2
+ can disable the vulnerability directly by declining to use printer
+ settings provided as part of ODF Documents:</p>
+
+ <ol><li>In Apache OpenOffice, select the Tools menu Options entry.</li>
+ <li>On the Options Load/Save item's General sub-item, remove any
+ check for "Load printer settings with the document".</li>
+ <li>Click "OK".</li>
+ <li>This setting will apply to all documents loaded thereafter.</li>
+ </ol>
+
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+ <p><strong>Credits</strong></p>
+ <p>
+ The discoverer of this vulnerability wishes to remain anonymous.<br >
+ Apache OpenOffice security team thanks Caolán McNamara of Red Hat for
+ analysis and a repair solution.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2015-5212.html">CVE-2015-5212</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2015-5213.html b/content/security/cves/CVE-2015-5213.html
new file mode 100644
index 0000000..ad30bb6
--- /dev/null
+++ b/content/security/cves/CVE-2015-5213.html
@@ -0,0 +1,104 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2015-5213</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-5213">CVE-2015-5213</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2015-5213.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2015-5213:
+ .DOC DOCUMENT VULNERABILITY</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.2</strong></p>
+
+ <p><strong>Title: Memory Corruption Vulnerability (DOC
+ Piecetable)</strong></p>
+ <p>
+ <strong>Version 1.0</strong>
+ <br />
+ Announced November 4, 2015</p>
+
+ <p>
+ A crafted Microsoft Word DOC file can be used to specify a
+ document buffer that is too small for the amount of data
+ provided for it. Failure to detect the discrepancy allows
+ an attacker to cause denial of service (memory corruption
+ and application crash) and possible execution of arbitrary
+ code.
+ </p>
+
+ <p>
+ <strong>Severity: Important</strong>
+ </p>
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.</p>
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong></p>
+
+ <p>All Apache OpenOffice versions 4.1.1 and older are affected.<br />
+ OpenOffice.org versions are also affected.</p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+ <p>Apache OpenOffice users are urged to download and install
+ Apache OpenOffice version 4.1.2 or later. DOC files having
+ the defect are detected and made ineffective in 4.1.2.
+ </p>
+
+ <p>
+ <strong>Precautions</strong>
+ </p>
+ <p>
+ Users who do not upgrade to Apache OpenOffice 4.1.2 should
+ be careful of .DOC files from unknown or unreliable sources.
+ A Microsoft Word 97-2003 DOC format file can be checked
+ by opening with software, such as Microsoft Office Word or
+ Word Online, that rejects documents having this defect as
+ corrupted.</p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+ <p><strong>Credits</strong></p>
+ <p>
+ The discoverer of this vulnerability wishes to remain anonymous.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2015-5213.html">CVE-2015-5213</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2015-5214.html b/content/security/cves/CVE-2015-5214.html
new file mode 100644
index 0000000..aeff7fd
--- /dev/null
+++ b/content/security/cves/CVE-2015-5214.html
@@ -0,0 +1,104 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2015-5214</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-5214">CVE-2015-5214</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2015-5214.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2015-5214:
+ .DOC BOOKMARKS VULNERABILITY</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.2</strong></p>
+
+ <p><strong>Title: Memory Corrruption Vulnerability (DOC
+ Bookmarks)</strong></p>
+ <p>
+ <strong>Version 1.0</strong>
+ <br />
+ Announced November 4, 2015</p>
+
+ <p>
+ A crafted Microsoft Word DOC can contain invalid bookmark
+ positions leading to memory corruption when the document is
+ loaded or bookmarks are manipulated. The defect allows an
+ attacker to cause denial of service (memory corruption and
+ application crash) and possible execution of arbitrary code.
+ </p>
+
+ <p>
+ <strong>Severity: Medium</strong>
+ </p>
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.</p>
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong></p>
+
+ <p>All Apache OpenOffice versions 4.1.1 and older are affected.<br />
+ OpenOffice.org versions are also affected.</p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+ <p>
+ Apache OpenOffice users are urged to download and install Apache
+ OpenOffice version 4.1.2 or later. The defect is over-ridden in
+ 4.1.2.
+ </p>
+
+ <p>
+ <strong>Precautions</strong>
+ </p>
+ <p>
+ Users who do not upgrade to Apache OpenOffice 4.1.2 should
+ be careful of .DOC files from unknown or unreliable sources.
+ A Microsoft Word 97-2003 DOC format file can be checked
+ by opening with software, such as Microsoft Office Word or
+ Word Online. The documents may be rejected as corrupted or
+ extraordinary employment of bookmarks may be observable.</p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+ <p><strong>Credits</strong></p>
+ <p>
+ The discoverer of this vulnerability wishes to remain anonymous.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/security/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2015-5214.html">CVE-2015-5214</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2016-1513.html b/content/security/cves/CVE-2016-1513.html
new file mode 100644
index 0000000..a552b30
--- /dev/null
+++ b/content/security/cves/CVE-2016-1513.html
@@ -0,0 +1,163 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2016-1513</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current wrapping
+ for the site introduces HTML5 headers and formats. This version is
+ modified to match the wrapping that is done as part of publishing
+ this page and not rely on any particular styling beyond <p>.
+ -->
+
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1513">
+ CVE-2016-1513</a>
+ </p>
+
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2016-1513.html">
+ Apache OpenOffice Advisory</a>
+ </p>
+
+ <p>
+ <strong>Memory Corruption Vulnerability (Impress Presentations)</strong>
+ </p>
+
+ <p>
+ <strong>Version 3.0</strong>
+ </p>
+
+ <p>
+ Updated October 11, 2016<br />
+ Updated August 30, 2016<br />
+ Announced July 21, 2016
+ </p>
+
+ <p>
+ <strong>Description</strong>
+ </p>
+
+ <p>
+ An OpenDocument Presentation .ODP or Presentation Template .OTP file
+ can contain invalid presentation elements that lead to memory
+ corruption when the document is loaded in Apache OpenOffice Impress.
+ The defect may cause the document to appear as corrupted and
+ OpenOffice may crash in a recovery-stuck mode requiring manual
+ intervention. A crafted exploitation of the defect can allow an
+ attacker to cause denial of service (memory corruption and
+ application crash) and possible execution of arbitrary code.
+ </p>
+ <p>Impress cannot be used to directly produce documents having the
+ CVE-2016-1513-related defect. Impress-authored .ODF and .ODT
+ documents of an user's own that exhibit any of these characteristics
+ are not the result of an exploit. They may be consequences
+ of a separate Impress defect that should be reported.
+ </p>
+
+ <p>
+ <strong>Severity: Medium</strong>
+ </p>
+
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.2 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.3 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>
+ <br /><br />
+ Users of Apache OpenOffice 4.1.2 that cannot update to 4.1.3
+ can Install the 4.1.2-patch1 Hotfix available at
+ <a href="http://archive.apache.org/dist/openoffice/4.1.2-patch1/hotfix.html">http://archive.apache.org/dist/openoffice/4.1.2-patch1/hotfix.html</a>.
+ <br /><br />
+ A source-code patch that blocks the vulnerability has been developed and is available for developers at <a href="https://bz.apache.org/ooo/show_bug.cgi?id=127045">issue 127045</a> with SVN revision
+ <a href="http://svn.apache.org/viewvc?view=revision&revision=1754535">1754535</a>.
+ <br /><br />
+ Antivirus products can detect documents attempting to exploit this vulnerability by employing Snort Signature IDs 35828-35829.
+ </p>
+
+ <p>
+ <strong>Defenses and Work-Arounds</strong>
+ </p>
+
+ <p>
+ If you are unable to update, there are other precautions that
+ can be taken. These precausions are recommended for all users
+ of all versions of Apache OpenOffice, including the latest
+ available.
+ <br /><br />
+ Avoid operating Apache OpenOffice (and any other personal
+ productivity programs) under a computer account that has
+ administrative privileges of any kind. While installation of
+ Apache OpenOffice requires elevated privileges and user permission
+ on platforms such as Microsoft Windows, operation of the software
+ does not.
+ <br /><br />
+ Keeping antivirus/antimalware software current is also important.
+ This will serve to identify and distinguish suspicious documents
+ that involve the exploit, avoiding confusion with documents that
+ are damaged and/or fail for other reasons.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+
+ <p>
+ For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice
+ Community Forums</a>, or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list. Defects not involving suspected security
+ vulnerabilities can be reported with a normal issue via
+ <a href="https://www.openoffice.org/qa/issue_handling/pre_submission.html">Bugzilla</a>.
+ </p>
+
+ <p>
+ The latest information on Apache OpenOffice security bulletins can
+ be found at the
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin Archive page</a>.
+ </p>
+
+ <p>
+ <strong>Credits</strong>
+ </p>
+
+ <p>
+ The Apache OpenOffice project acknowledges the discovery and analysis for CVE-2016-1513 by Yves Younan and Richard Johnson of Cisco Talos.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="https://www.openoffice.org/security/">Security Home</a>
+ -> <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2016-1513.html">
+ CVE-2016-1513</a>
+ </p>
+
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2016-6803.html b/content/security/cves/CVE-2016-6803.html
new file mode 100644
index 0000000..79437c7
--- /dev/null
+++ b/content/security/cves/CVE-2016-6803.html
@@ -0,0 +1,153 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2016-6803</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current wrapping
+ for the site introduces HTML5 headers and formats. This version is
+ modified to match the wrapping that is done as part of publishing
+ this page and not rely on any particular styling beyond <p>.
+ -->
+
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-6803">
+ CVE-2016-6803</a>
+ </p>
+
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2016-6803.html">
+ Apache OpenOffice Advisory</a>
+ </p>
+
+ <p>
+ <strong>Windows Installer Can Enable Privileged Trojan Execution
+ </strong>
+ </p>
+
+ <p>
+ <strong>Version 1.0</strong>
+ </p>
+
+ <p>
+ Announced October 11, 2016
+ </p>
+
+ <p>
+ <strong>Description</strong>
+ </p>
+
+ <p>
+ The Apache OpenOffice installer for Winodws contained a defective
+ operation that could trigger execution of unwanted software
+ installed by a Trojan Horse application. The installer defect
+ is known as an "unquoted Windows search path vulnerability."
+ </p>
+ <p>
+ In the case of Apache OpenOffice installers for Windows, the PC
+ must have previously been infected by a Trojan Horse application
+ (or user) running with administrative privilege. Any installer
+ with the unquoted search path vulnerability becomes a delayed
+ trigger for the exploit. The exploit may already have operated
+ on the user's PC.
+ </p>
+
+ <p>
+ <strong>Severity: Medium</strong>
+ </p>
+
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.2 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.3 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ <br /><br />
+ If instead of a typical installation you use a custom-installation
+ option to change the location where Apache OpenOffice is installed,
+ use a location that has no spaces in its full-path name.
+ </p>
+
+ <p>
+ <strong>Defenses and Work-Arounds</strong>
+ </p>
+
+ <p>
+ If you are unable to update to 4.1.3, there are other precautions
+ that can be taken. These precausions are also recommended as protection against other software that may have the vulnerability.
+ <br /><br />
+ Ensure that there are no programs installed at the top-level folder
+ (usually C:\) where Windows is installed. All are dangerous,
+ especially ones named "Program", whether "Program.exe" or some
+ other variation.
+ <br /><br />
+ If such programs are found, install or update to current
+ anti-virus/-malware software. Perform a complete system scan.
+ The scan may provide for removal of programs where there should
+ not be any. If that does not happen, it is necessary to remove
+ any Program.exe and others manually using administrator privilege.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+
+ <p>
+ For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice
+ Community Forums</a>, or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list. Defects not involving suspected security
+ vulnerabilities can be reported with a normal issue via
+ <a href="https://www.openoffice.org/qa/issue_handling/pre_submission.html">Bugzilla</a>.
+ </p>
+
+ <p>
+ The latest information on Apache OpenOffice security bulletins can
+ be found at the
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin Archive page</a>.
+ </p>
+
+ <p>
+ <strong>Credits</strong>
+ </p>
+
+ <p>
+ The Apache OpenOffice project acknowledges the reporting and
+ analysis for CVE-2016-6803 by Cyril Vallicari.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="https://www.openoffice.org/security/">Security Home</a>
+ -> <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2016-1513.html">
+ CVE-2016-1513</a>
+ </p>
+
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2016-6804.html b/content/security/cves/CVE-2016-6804.html
new file mode 100644
index 0000000..78c6e54
--- /dev/null
+++ b/content/security/cves/CVE-2016-6804.html
@@ -0,0 +1,146 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2016-6804</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current wrapping
+ for the site introduces HTML5 headers and formats. This version is
+ modified to match the wrapping that is done as part of publishing
+ this page and not rely on any particular styling beyond <p>.
+ -->
+
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-6804">
+ CVE-2016-6804</a>
+ </p>
+
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2016-6804.html">
+ Apache OpenOffice Advisory</a>
+ </p>
+
+ <p>
+ <strong>Windows Installer Execution of Arbitrary Code with
+ Elevated Privileges
+ </strong>
+ </p>
+
+ <p>
+ <strong>Version 1.0</strong>
+ </p>
+
+ <p>
+ Announced October 11, 2016
+ </p>
+
+ <p>
+ <strong>Description</strong>
+ </p>
+
+ <p>
+ The Apache OpenOffice installer for Winodws contained a defective
+ operation that allows execution of arbitrary code with elevated
+ privileges.
+ </p>
+ <p>The location in which the installer is run may have been
+ previously poisoned by a file that impersonates a dynamic-link
+ library that the installer depends upon. The counterfeit is
+ operated instead because of a search path defect in the
+ installer. The counterfeit will be operated under the
+ administrative privileges of the OpenOffice installer,
+ compromising the users's PC.
+ </p>
+
+ <p>
+ <strong>Severity: Medium</strong>
+ </p>
+
+ <p>There are no known exploits of this vulnerabilty.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.2 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.3 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ </p>
+
+ <p>
+ <strong>Defenses and Work-Arounds</strong>
+ </p>
+
+ <p>
+ If you are unable to update to 4.1.3, there are other precautions
+ that can be taken. These precausions are also recommended as protection against other software that may have the vulnerability.
+ <br /><br />
+ When executing .exe installers, ensure that the installer is in a file folder that has no other files but the installer .exe file.
+ <br /><br />
+ If an installer proposes a folder to extract the setup files
+ into before the actual install, choose the name of a folder that is not in use. Delete such a folder of setup files after the installation completes successfully. To reinstall without
+ downloading again, preserve the installer .exe on private
+ removable storage.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+
+ <p>
+ For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice
+ Community Forums</a>, or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list. Defects not involving suspected security
+ vulnerabilities can be reported with a normal issue via
+ <a href="https://www.openoffice.org/qa/issue_handling/pre_submission.html">Bugzilla</a>.
+ </p>
+
+ <p>
+ The latest information on Apache OpenOffice security bulletins can
+ be found at the
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin Archive page</a>.
+ </p>
+
+ <p>
+ <strong>Credits</strong>
+ </p>
+
+ <p>
+ The Apache OpenOffice project acknowledges the reporting and
+ analysis for CVE-2016-6804 by Stefan Kanthak and by Himanshu
+ Mehta.
+ </p>
+
+ <hr />
+
+ <p>
+ <a href="https://www.openoffice.org/security/">Security Home</a>
+ -> <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2016-1513.html">
+ CVE-2016-1513</a>
+ </p>
+
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2017-12607.html b/content/security/cves/CVE-2017-12607.html
new file mode 100644
index 0000000..44f5d9d
--- /dev/null
+++ b/content/security/cves/CVE-2017-12607.html
@@ -0,0 +1,79 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2017-12607</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-12607">CVE-2017-12607</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2017-12607.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2017-12607:
+ Out-of-Bounds Write in Impress' PPT Filter</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.4</strong></p>
+
+ <p><strong>Description</strong></p>
+
+ <p>A vulnerability in OpenOffice's PPT file parser, and specifically in PPTStyleSheet, allows attackers to craft malicious documents that cause denial of service (memory corruption and application crash) potentially resulting in arbitrary code execution.</p>
+
+ <p><strong>Severity: Medium</strong></p>
+
+ <p>There are no known exploits of this vulnerability.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>Thanks to Marcin 'Icewall' Noga of Cisco Talos for discovering this issue.</p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.3 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.4 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2017-12607.html">CVE-2017-12607</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2017-12608.html b/content/security/cves/CVE-2017-12608.html
new file mode 100644
index 0000000..1061368
--- /dev/null
+++ b/content/security/cves/CVE-2017-12608.html
@@ -0,0 +1,79 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2017-12608</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-12608">CVE-2017-12608</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2017-12608.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2017-12608:
+ Out-of-Bounds Write in Writer's ImportOldFormatStyles</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.4</strong></p>
+
+ <p><strong>Description</strong></p>
+
+ <p>A vulnerability in OpenOffice Writer DOC file parser, and specifically in ImportOldFormatStyles, allows attackers to craft malicious documents that cause denial of service (memory corruption and application crash) potentially resulting in arbitrary code execution.</p>
+
+ <p><strong>Severity: Medium</strong></p>
+
+ <p>There are no known exploits of this vulnerability.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>Thanks to Marcin 'Icewall' Noga of Cisco Talos for discovering this issue.</p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.3 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.4 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2017-12608.html">CVE-2017-12608</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2017-3157.html b/content/security/cves/CVE-2017-3157.html
new file mode 100644
index 0000000..747c9fe
--- /dev/null
+++ b/content/security/cves/CVE-2017-3157.html
@@ -0,0 +1,93 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2017-3157</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3157">CVE-2017-3157</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2017-3157.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2017-3157:
+ Arbitrary file disclosure in Calc and Writer</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.4</strong></p>
+
+ <p>
+ <strong>Description</strong>
+ </p>
+
+ <p>By exploiting the way OpenOffice renders embedded objects, an attacker could craft a document
+ that allows reading in a file from the user's filesystem. Information could be retrieved by the
+ attacker by, e.g., using hidden sections to store the information, tricking the user into
+ saving the document and convincing the user to sent the document back to the attacker.</p>
+
+ <p>The vulnerability is mitigated by the need for the attacker to know the precise file path
+ in the target system, and the need to trick the user into saving the document and sending it
+ back.</p>
+
+ <p><strong>Severity: Medium</strong></p>
+
+ <p>There are no known exploits of this vulnerability.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>Thanks to Ben Hayak for reporting this issue.</p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.3 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.4 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ </p>
+
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2017-3157.html">CVE-2017-3157</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2017-9806.html b/content/security/cves/CVE-2017-9806.html
new file mode 100644
index 0000000..092144d
--- /dev/null
+++ b/content/security/cves/CVE-2017-9806.html
@@ -0,0 +1,85 @@
+
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2017-9806</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <!-- These were previously defined as XHTML pages. The current
+ wrapping for the site introduces HTML5 headers and formats.
+ This version is modified to match the wrapping that is done as part
+ of publishing this page and not rely on any particular styling
+ beyond <p>.
+ -->
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9806">CVE-2017-9806</a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2017-9806.html">Apache OpenOffice Advisory</a>
+ </p>
+
+ <p style="text-align:center; font-size:largest"><strong>CVE-2017-9806:
+ Out-of-Bounds Write in Writer's WW8Fonts Constructor</strong></p>
+
+ <p style="text-align:center; font-size:larger"><strong>Fixed in Apache OpenOffice 4.1.4</strong></p>
+
+ <p><strong>Description</strong></p>
+
+ <p>A vulnerability in the OpenOffice Writer DOC file parser, and specifically in the WW8Fonts Constructor, allows attackers to craft malicious documents that cause denial of service (memory corruption and application crash) potentially resulting in arbitrary code execution.</p>
+
+ <p><strong>Severity: Medium</strong></p>
+
+ <p>There are no known exploits of this vulnerability.<br />
+ A proof-of-concept demonstration exists.
+ </p>
+
+ <p>Thanks to Marcin 'Icewall' Noga of Cisco Talos for discovering this issue.</p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.3 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.4 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">Apache OpenOffice Community Forums</a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">users@openoffice.apache.org</a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the <a href="https://www.openoffice.org/security/bulletin.html">Bulletin
+ Archive page</a>.</p>
+
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a>
+ -> <a href="http://security.openoffice.org/bulletin.html">Bulletin</a>
+ -> <a href="https://www.openoffice.org/security/cves/CVE-2017-9806.html">CVE-2017-9806</a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2018-11790.html b/content/security/cves/CVE-2018-11790.html
new file mode 100644
index 0000000..6a29c48
--- /dev/null
+++ b/content/security/cves/CVE-2018-11790.html
@@ -0,0 +1,106 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2018-11790</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <p>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11790">
+ CVE-2018-11790
+ </a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2018-11790.html">
+ Apache OpenOffice Advisory
+ </a>
+ </p>
+
+ <p style="text-align:center; font-size:largest">
+ <strong>CVE-2018-11790 Arithmetic overflow and wrap around during
+ sting length calculation
+ </strong>
+ </p>
+
+ <p style="text-align:center; font-size:larger">
+ <strong>Fixed in Apache OpenOffice 4.1.6</strong>
+ </p>
+
+ <p><strong>Description</strong></p>
+
+
+ <p> When loading a document with smaller end line termination then the
+ operating system uses, the defect occurs.
+ In this case OpenOffice runs into an Arithmetic Overflow at a string
+ length calculation.
+ </p>
+
+ <p><strong>Severity: Medium</strong></p>
+
+ <p>There are no known exploits of this vulnerability.<br />
+ A proof-of-concept demonstration exists.</br>
+ <a href=https://ssd-disclosure.com/index.php/archives/3758>
+ ssd-disclosure
+ </a>
+ </p>
+
+ <p>Thanks to the reporter for discovering this issue.</p>
+
+ <p>
+ <strong>Vendor: The Apache Software Foundation</strong>
+ </p>
+
+ <p>
+ <strong>Versions Affected</strong>
+ </p>
+
+ <p>
+ All Apache OpenOffice versions 4.1.5 and older are affected.<br />
+ OpenOffice.org versions are also affected.
+ </p>
+
+ <p>
+ <strong>Mitigation</strong>
+ </p>
+
+ <p>
+ Install Apache OpenOffice 4.1.6 for the latest maintenance and
+ cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">download page</a>.
+ </p>
+
+ <p>
+ <strong>Further Information</strong>
+ </p>
+ <p>For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">
+ Apache OpenOffice Community Forums
+ </a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">
+ users@openoffice.apache.org
+ </a>
+ public mailing list.
+ </p>
+ <p>The latest information on Apache OpenOffice security bulletins
+ can be found at the
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin Archive page
+ </a>.
+ </p>
+
+
+ <hr />
+
+ <p>
+ <a href="http://security.openoffice.org">Security Home</a> ->
+ <a href="http://www.openoffice.org/security/bulletin.html">
+ Bulletin
+ </a> ->
+ <a href="https://www.openoffice.org/security/cves/CVE-2018-11790.html">
+ CVE-2018-11790
+ </a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-2019-9853.html b/content/security/cves/CVE-2019-9853.html
new file mode 100644
index 0000000..234eb27
--- /dev/null
+++ b/content/security/cves/CVE-2019-9853.html
@@ -0,0 +1,129 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-2019-9853</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <p>
+ <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9853">
+ CVE-2019-9853
+ </a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-2019-9853.html">
+ Apache OpenOffice Advisory
+ </a>
+ </p>
+ <p style="text-align:center; font-size:larger">
+ <strong>
+ CVE-2019-9853 Insufficient URL decoding flaw in categorizing macro location
+ </strong>
+ </p>
+ <p style="text-align:center; font-size:larger">
+ <strong>
+ Fixed in Apache OpenOffice 4.1.7
+ </strong>
+ </p>
+ <p>
+ <strong>
+ Description
+ </strong>
+ </p>
+ <p>
+ OpenOffice documents can contain macros. The execution of those macros is controlled by the document security settings,
+ typically execution of macros are blocked by default. A URL decoding flaw existed in how the URLs to the macros within
+ the document were processed and categorized, resulting in the possibility to construct a document where macro execution
+ bypassed the security settings. The documents were correctly detected as containing macros, and prompted the user to
+ their existence within the documents, but macros within the document were subsequently not controlled by the security
+ settings allowing arbitrary macro execution.
+ This issue affects: OpenOffice 4.1.6 and older versions.
+ </p>
+ <p>
+ <strong>
+ Severity: Medium
+ </strong>
+ </p>
+ <p>
+ There are no known exploits of this vulnerability.
+ <br />
+ A proof-of-concept demonstration exists.
+ </p>
+ <p>
+ Thanks to the reporter for discovering this issue.
+ </p>
+ <p>
+ <strong>
+ Vendor: The Apache Software Foundation
+ </strong>
+ </p>
+ <p>
+ <strong>
+ Versions Affected
+ </strong>
+ </p>
+ <p>
+ All Apache OpenOffice versions 4.1.6 and older are affected.
+ <br />
+ OpenOffice.org versions may also be affected.
+ </p>
+ <p>
+ <strong>
+ Mitigation
+ </strong>
+ </p>
+ <p>
+ Install Apache OpenOffice 4.1.7 for the latest maintenance and cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">
+ download page
+ </a>.
+ </p>
+ <p>
+ <strong>
+ Acknowledgments
+ </strong>
+ </p>
+ <p>
+ The Apache OpenOffice Security Team would like to thank
+ Nils Emmerich (ERNW Research GmbH)
+ for reporting the issue.
+ </p>
+ <p>
+ <strong>
+ Further Information
+ </strong>
+ </p>
+ <p>
+ For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">
+ Apache OpenOffice Community Forums
+ </a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">
+ users@openoffice.apache.org
+ </a>
+ public mailing list.
+ </p>
+ <p>
+ The latest information on Apache OpenOffice security bulletins can be found at the
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin Archive page
+ </a>.
+ </p>
+ <hr />
+ <p>
+ <a href="https://security.openoffice.org">
+ Security Home
+ </a>
+ ->
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin
+ </a>
+ ->
+ <a href="https://www.openoffice.org/security/cves/CVE-2019-9853.html">
+ CVE-2019-9853
+ </a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-XXXX-YYYY.html b/content/security/cves/CVE-XXXX-YYYY.html
new file mode 100644
index 0000000..3b22e77
--- /dev/null
+++ b/content/security/cves/CVE-XXXX-YYYY.html
@@ -0,0 +1,123 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>CVE-XXXX-YYYY</title>
+ <style type="text/css"></style>
+ </head>
+
+ <body>
+ <p>
+ <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=XXXX-YYYY">
+ CVE-XXXX-YYYY
+ </a>
+ </p>
+ <p>
+ <a href="https://www.openoffice.org/security/cves/CVE-XXXX-YYYY.html">
+ Apache OpenOffice Advisory
+ </a>
+ </p>
+ <p style="text-align:center; font-size:larger">
+ <strong>
+ CVE-XXXX-YYYY: VULNERABILITY DESCRIPTION
+ </strong>
+ </p>
+ <p style="text-align:center; font-size:larger">
+ <strong>
+ Fixed in Apache OpenOffice x.y.z
+ </strong>
+ </p>
+ <p>
+ <strong>
+ Description
+ </strong>
+ </p>
+ <p>
+ This is a test page for confirming that formatting is working as expected.
+ </p>
+ <p>
+ <strong>
+ Severity: Medium
+ </strong>
+ </p>
+ <p>
+ There are no known exploits of this vulnerability.
+ <br />
+ A proof-of-concept demonstration exists.
+ </p>
+ <p>
+ Thanks to ... for discovering this issue.
+ </p>
+ <p>
+ <strong>
+ Vendor: The Apache Software Foundation
+ </strong>
+ </p>
+ <p>
+ <strong>
+ Versions Affected
+ </strong>
+ </p>
+ <p>
+ All Apache OpenOffice versions x.y.t and older are affected.
+ <br />
+ OpenOffice.org versions may also be affected.
+ </p>
+ <p>
+ <strong>
+ Mitigation
+ </strong>
+ </p>
+ <p>
+ Install Apache OpenOffice x.y.z for the latest maintenance and cumulative security fixes. Use the Apache OpenOffice
+ <a href="https://www.openoffice.org/download/">
+ download page
+ </a>.
+ </p>
+ <p>
+ <strong>
+ Acknowledgments
+ </strong>
+ </p>
+ <p>
+ The Apache OpenOffice Security Team would like to thank
+ an anonymous researcher
+ for reporting the issue.
+ </p>
+ <p>
+ <strong>
+ Further Information
+ </strong>
+ </p>
+ <p>
+ For additional information and assistance, consult the
+ <a href="https://forum.openoffice.org/">
+ Apache OpenOffice Community Forums
+ </a>
+ or make requests to the
+ <a href="mailto:users@openoffice.apache.org">
+ users@openoffice.apache.org
+ </a>
+ public mailing list.
+ </p>
+ <p>
+ The latest information on Apache OpenOffice security bulletins can be found at the
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin Archive page
+ </a>.
+ </p>
+ <hr />
+ <p>
+ <a href="https://security.openoffice.org">
+ Security Home
+ </a>
+ ->
+ <a href="https://www.openoffice.org/security/bulletin.html">
+ Bulletin
+ </a>
+ ->
+ <a href="https://www.openoffice.org/security/cves/CVE-XXXX-YYYY.html">
+ CVE-XXXX-YYYY
+ </a>
+ </p>
+ </body>
+</html>
diff --git a/content/security/cves/CVE-YYYY-XXXX.html b/content/security/cves/CVE-YYYY-XXXX.html
new file mode 100755
index 0000000..51603c8
--- /dev/null
+++ b/content/security/cves/CVE-YYYY-XXXX.html
@@ -0,0 +1,63 @@
+<!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-YYYY-XXXX</title>
+ <style type="text/css"></style>
+</head>
+
+<body>
+ <h2><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=YYYY-XXXX">CVE-YYYY-XXXX</a></h2>
+
+ <h3>
+ Security vulnerability in OpenOffice.org related to XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ </h3>
+
+ <ul>
+ <li><strong>Synopsis:</strong>
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ </li>
+ <li><strong>State:</strong> Resolved</li>
+ </ul>
+
+ <h4>1. Impact</h4>
+
+ <p>
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ </p>
+
+ <h4>2. Affected releases</h4>
+
+ <ul>
+ <li>All versions of OpenOffice.org 3 prior to version 3.3</li>
+ <li>All versions of OpenOffice.org 2</li>
+ </ul>
+
+ <p>Note: Earlier versions of OpenOffice.org are no longer supported and will not be evaluated regarding this issue.</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>
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ </p>
+
+ <h4>5. Resolution</h4>
+
+ <p>This issue is addressed in the following release: <strong>OpenOffice.org 3.3</strong></p>
+
+ <h4>6. Comments</h4>
+
+ <p>
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ </p>
+
+ <hr />
+
+ <p><a href="//security/">Security Home</a> -> <a href="//security/bulletin.html">Bulletin</a> ->
+ <a href="//security/cves/CVE-YYYY-XXXX.html">CVE-YYYY-XXXX</a></p>
+</body>
+</html>
diff --git a/content/security/cves/index.html b/content/security/cves/index.html
new file mode 100644
index 0000000..60204c8
--- /dev/null
+++ b/content/security/cves/index.html
@@ -0,0 +1,8 @@
+<html>
+<head>
+<meta http-equiv="refresh" content="0; url=https://www.openoffice.org/security/bulletin.html">
+</head>
+<body>
+<p>See <a href="https://www.openoffice.org/security/bulletin.html">https://www.openoffice.org/security/bulletin.html</a></p>
+</body>
+</html>
diff --git a/content/security/faq.html b/content/security/faq.html
new file mode 100644
index 0000000..e4d6e7b
--- /dev/null
+++ b/content/security/faq.html
@@ -0,0 +1,192 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+
+ <title>Apache OpenOffice Security Team FAQ</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+</head>
+
+<body>
+ <a id="top" name="top"></a>
+
+ <h2>Apache OpenOffice Security Team FAQ</h2>
+
+ <ul>
+ <li><a href="#secure">Is OpenOffice secure?</a></li>
+
+ <li><a href="#genuine">How do I know my copy of OpenOffice is
+ genuine?</a></li>
+
+ <li><a href="#protect">How do I protect my copy of OpenOffice against
+ security issues?</a></li>
+
+ <li><a href="#verify">"The publisher of this software cannot be verified"
+ - what should I do?</a></li>
+
+ <li><a href="#viruses">How do I stop viruses attacking my copy of
+ OpenOffice?</a></li>
+
+ <li><a href="#macros">How do I protect against macro-viruses in
+ OpenOffice?</a></li>
+
+ <li><a href="#reporting">I am a developer - how do I report a security
+ vulnerability in OpenOffice?</a></li>
+
+ <li><a href="#bulletin">Where can I find a list of all the security
+ vulnerabilities fixed in OpenOffice?</a></li>
+
+ <li><a href="#alerts">How can I get email alerts about security
+ vulnerabilities fixed in OpenOffice?</a></li>
+ </ul><a id="secure" name="secure"></a>
+
+ <h3>Is OpenOffice secure?</h3>
+
+ <p>The OpenOffice engineers take the security of the software very
+ seriously. We take great care to ensure that our software is secure, and we
+ will react promptly to any reports of suspected security vulnerabilities in
+ our software.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="genuine" name="genuine"></a>
+
+ <h3>How do I know my copy of OpenOffice is genuine?</h3>
+
+ <p>Make sure you know where your copy of OpenOffice has come from.
+ Download from one of the sites listed in <a href=
+ "/download">our download page</a>, or purchase from
+ one of our CD distributors.
+ <a href="../download/checksums.html">Use a checksum</a>
+ to make sure your copy has not been corrupted before you install it.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="protect" name="protect"></a>
+
+ <h3>How do I protect my copy of OpenOffice against security
+ issues?</h3>
+
+ <p>We recommend all users install new versions of OpenOffice as soon as
+ practical after they are released. Since version 2.1, OpenOffice has
+ included a feature which will tell you if a new version is available. We
+ recommend you switch this on <em>(Tools -> Options -> Online Update
+ -> Check for updates automatically)</em>.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="verify" name="verify"></a>
+
+ <h3>"The publisher of this software cannot be verified" - what should I
+ do?</h3>
+
+ <p>When installing OpenOffice under Microsoft Windows, you may see a
+ warning message stating that the publisher of the software could not be
+ verified. It is safe to ignore this message if you are confident that your
+ copy of OpenOffice came from a reputable source. If you have any doubts
+ about this, you can check that the file has not been tampered with by
+ <a href="../download/checksums.html">using MD5 checksums</a>.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="viruses" name="viruses"></a>
+
+ <h3>How do I stop viruses attacking my copy of OpenOffice?</h3>
+
+ <p>If your computer becomes infected with a virus, it is possible that any
+ program you have installed – including OpenOffice - may become
+ corrupted. Your computer cannot catch a virus from fresh air. It can become
+ infected if someone gives you any kind of media – floppy disk, CD, DVD,
+ memory stick, memory card etc. – anything capable of holding data can also
+ hold a virus. It can become infected if it is connected to any kind of
+ network, including wireless. Connections to publicly accessible networks
+ like the internet are particularly risky.</p>
+
+ <p>There is a whole range of things you can do to protect your computer –
+ firewalls, anti-virus software, etc – please contact your PC supplier or IT
+ department for details. If you suspect your PC has been infected, please
+ seek specialist support.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="macros" name="macros"></a>
+
+ <h3>How do I protect against macro-viruses in OpenOffice?</h3>
+
+ <p>Macros are a useful part of any office suite, allowing you to automate
+ repetitive tasks. A macro can do anything you can do - including
+ potentially destructive actions such as modifying and deleting files. A
+ macro can attached to any OpenOffice file (document, spreadsheet,
+ etc.).</p>
+
+ <p>Whenever OpenOffice detects macros in a document being opened, by
+ default it displays a warning and will only run the macro if the you
+ specifically agree.</p>
+
+ <p>The safest rule is you should never open any OpenOffice file unless
+ you are sure where it has come from and trust the sender. Note that it is
+ very easy to falsify an email address - if you have any doubt, do not open
+ the document until you have proved its identity. If you need to exchange
+ documents regularly, we recommend the use of digital signatures to certify
+ the origin of the document.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="reporting" name="reporting"></a>
+
+ <h3>I am a developer - how do I report a security vulnerability in
+ OpenOffice?</h3>
+
+ <p>Please report any suspected vulnerabilities to our <a href=
+ "mailto:security@openoffice.apache.org">Security Team</a>. We appreciate
+ early confidential disclosure to give vendors of products and solutions
+ based on OpenOffice time to react. We will coordinate the disclosure of
+ your report with you.</p>
+
+ <p>In your report, please include the following information:</p>
+
+ <ul>
+ <li>In which version of OpenOffice did you identify the problem (e.g.
+ 3.3.0, 3.4.1, 4.0.0, etc.)?</li>
+
+ <li>What is the impact of the problem (data loss, denial of service,
+ executing commands, etc.)?</li>
+
+ <li>How can the problem be reproduced?</li>
+
+ <li>Is there an existing exploit?</li>
+
+ <li>Has the problem already been published?</li>
+ </ul>
+
+ <p>After we receive your report, we will work on the evaluation and we will
+ reply to you (typically in the next business day).</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="bulletin" name="bulletin"></a>
+
+ <h3>Where can I find a list of all the security vulnerabilities fixed in
+ OpenOffice?</h3>
+
+ <p>These are listed in our <a href=
+ "/security/bulletin.html">Security
+ Bulletin</a>.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p><a id="alerts" name="alerts"></a>
+
+ <h3>How can I get email alerts about security vulnerabilities fixed in
+ OpenOffice?</h3>
+
+ <p>Please read our <a href=
+ "/security/alerts.html">Security Alerts</a>
+ page.</p>
+
+ <p><a href="#top"><img src="top.gif" alt="up arrow" /> Return to
+ top</a></p>
+ <hr />
+
+ <p><a href="/security/">Security Home</a> ->
+ <a href="/security/faq.html">Security FAQ</a></p>
+</body>
+</html>
diff --git a/content/security/index.html b/content/security/index.html
new file mode 100755
index 0000000..b36c874
--- /dev/null
+++ b/content/security/index.html
@@ -0,0 +1,67 @@
+<!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>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+
+ <title>Apache OpenOffice Security Team</title>
+ <style type="text/css">
+/*<![CDATA[*/
+ hr { display: block }
+ /*]]>*/
+ </style>
+
+</head>
+
+<body>
+ <h2>Apache OpenOffice Security Team</h2>
+
+ <p>For general information about Apache OpenOffice security, please see our
+ <a href="/security/faq.html">Frequently Asked
+ Questions page</a>.</p>
+
+ <p>For details of our security alerts by email service, please see our
+ <a href="alerts.html">Security Alerts page</a>.</p>
+
+ <p>OpenOffice is a complex piece of software developed by various
+ teams. As such, it can contain security relevant bugs. If you are a
+ software developer and you believe you have found a vulnerability in our
+ source code, please contact our <a href=
+ "mailto:security@openoffice.apache.org">security team</a> so we can evaluate
+ the problem and work on proper solution for our users and for future
+ versions of our product.</p>
+
+ <p>We appreciate early confidential disclosure to give vendors of products
+ and solutions based on OpenOffice time to react. We will coordinate the
+ disclosure of your report with you.</p>
+
+ <p>In your report, please include the following informations:</p>
+
+ <ul>
+ <li>In which version of OpenOffice did you identify the problem?</li>
+
+ <li>Do you have an official version of OpenOffice or e.g. a build
+ from your GNU/Linux distribution (include the URL of the build if
+ possible)?</li>
+
+ <li>What is the impact of the problem (data loss, denial of service,
+ executing commands, etc.)?</li>
+
+ <li>How can the problem be reproduced?</li>
+
+ <li>Is there an existing exploit?</li>
+
+ <li>Has the problem already been published?</li>
+ </ul>
+
+ <p>After we receive your report, we will work on the evaluation and we will
+ reply to you (typically in the next business days).</p>
+
+ <p>Vulnerabilities which have been resolved are listed in our <a href=
+ "bulletin.html">Bulletin</a>.</p>
+ <hr />
+
+ <p><a href="/security/">Security Home</a></p>
+</body>
+</html>
diff --git a/content/security/response_to_defence_ministry_leak.html b/content/security/response_to_defence_ministry_leak.html
new file mode 100644
index 0000000..632c8c3
--- /dev/null
+++ b/content/security/response_to_defence_ministry_leak.html
@@ -0,0 +1,37 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Untitled Document</title>
+</head>
+
+<body>
+<h2> Response To The French Ministry of Defence Report Leak </h2>
+<p>2006-07-20</p>
+<p>There has been comment in the media about a report on a French language
+ website: "Le ministère de la Défense met OpenOffice à l'index"
+</p>
+<p>The <a href="http://www.zdnet.fr/actualites/informatique/0,39040745,39362096,00.htm">ZDNet article</a> claims to describe the proceedings of a confidential
+ meeting within the French public administration. It is not appropriate for
+ the OpenOffice.org community to comment on a leak from a private meeting.
+ However, one of the people mentioned in the article, Eric Filiol, has
+ posted two replies to the online article clarifying the purpose of the
+ research and correcting some of the incorrect conclusions in the original
+ article.</p>
+<p>The OpenOffice.org office suite is being widely adopted within the French
+ public administration, and the OpenOffice.org community has been working
+ closely with the departments involved. OpenOffice.org is pleased that its
+ source code is being scrutinised by the most important and respected
+ department of security in France.</p>
+<p>If security vulnerabilities are suspected, there is a well defined
+ procedure within the IT industry for reporting, analysing, and resolving
+ any issues, which aims to minimise any public announcement (and the
+ resulting creation of exploits) until fixes are available.</p>
+<p>The OpenOffice.org community confirms it regards security as of the
+ highest importance and will react immediately to any security issues
+ reported by the French public adminstration or other competent bodies or
+ individuals.</p>
+<p>-The OpenOffice.org Team </p>
+</body>
+</html>