Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to firstname.lastname@example.org
Score: 1 Posts: 109 User Since: 11th Feb 2009 System Score: 100% Location: US Last edited on 19th Feb, 2010 23:05
I found I did not need to install a Release Candidate to resolve this issue.
"Check for Updates" in OpenOffice release 3.1.1 OOO310m19 (build:9420) reported that OpenOffice 3.1 is up to date. It did not offer to install 3.2.
Clicking Secunia PSI's "Download Solution" button displayed a "Download OpenOffice.org 3.2.0" button. The button downloaded OpenOffice.org release 3.2.0 OOO320_m12 (build:9483). A Get Release Candidate button was also present but I did not use it.
Installing the downloaded release cleared the PSI vulnerability report.
Score: 2372 Posts: 3,280 User Since: 19th Dec 2007 System Score: N/A Location: N/A
Just to be clear , in the programme's "help" dropdown menu , the version shown in "about" as "OpenOffice.org release 3.2.0 OOO320_m12 (build:9483)" is shown in Secunia PSI "patched" tab as version 3.2.9476.500 - the detection rules (presumably) using version numbers found (mouse over , if you wish to check) on certain files in the OOo main folder. This was the same for 3.0. and 3.1 . The build N° is "usually" the guiding factor .
AFAIK this is the latest stable release (English language) as officially offered by OOo and not an RC .
It always seems impossible until its done.
Was this reply relevant?
You must be logged in to post a comment.
Secunia Customer Login
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.