Author: buildbot
Date: Wed May 16 14:38:42 2012
New Revision: 817932

Log:
Staging update by buildbot for openofficeorg

Modified:
    websites/staging/ooo-site/trunk/cgi-bin/   (props changed)
    websites/staging/ooo-site/trunk/content/   (props changed)
    websites/staging/ooo-site/trunk/content/security/cves/CVE-2012-2149.html

Propchange: websites/staging/ooo-site/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 16 14:38:42 2012
@@ -1 +1 @@
-1339169
+1339188

Propchange: websites/staging/ooo-site/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 16 14:38:42 2012
@@ -1 +1 @@
-1339169
+1339188

Modified: 
websites/staging/ooo-site/trunk/content/security/cves/CVE-2012-2149.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/security/cves/CVE-2012-2149.html 
(original)
+++ websites/staging/ooo-site/trunk/content/security/cves/CVE-2012-2149.html 
Wed May 16 14:38:42 2012
@@ -42,14 +42,14 @@
 
 <h4>Description:</h4>
 <p>
-Description: Effected versions of OpenOffice.org use a customized libwpd that 
has an memory overwrite vulnerability that could be exploited by
+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 oppening untrusted WPD documents.</p>
+cautious when opening untrusted WPD documents.</p>
 
 <h4>Credits</h4>
 


Reply via email to