Filed under: Security, Windows, Macintosh, Linux, OpenOffice.org
New OpenOffice bug affects Mac, Linux, as well as Windows
OpenOffice's developers have not yet released a fix for the bug (update: the bug does not exist in version 2.3 or newer), but the firm that discovered it is advising OpenOffice users to "be careful" with attachments received from unknown sources. Good advice--whether you run OpenOffice, Microsoft Office, or Wordstar.

Get a WordPress.com Blog
With Halloween fast approaching, it's a great time to get in some practice defending your territory against zombies. In Graveyard Shift, you take aim at zombies and other creepy-crawlies, blasting them into splatters of cartoony green guts. It's a casual first-person shooter, and it's very easy to get the hang of - use the mouse to aim, click to fire. Graveyard Shift has at least 15 levels, and it might even have some secret stages I haven't unlocked yet.
They key to getting good at Graveyard Shift is learning to use ...

Reader Comments (Page 1 of 1)
Chuck said 9:35PM on 9-25-2007
But according to the ZDNet article: "The next version of OpenOffice (version 2.3) arrived on 17 September and is not affected by the flaw."
I installed 2.3, so I shouldn't be worried about this bug, correct?
Reply
James Roche said 1:49AM on 9-26-2007
Maybe it would be kind to acknowledge the following:
1) It's taken a really long time for someone to discover, and no one yet has taken the opportunity to employ, this flaw.
2) The latest version already includes a patch.
This story comes across as a bit of a "just as bad as Microsoft" hit job. The fact is, when civilians find hackable flaws in Windows or IE, the fixes are insufferable and frequently ignored for a duration. This announcement is more noble than shameful, the Open Office movement deserves a retraction.
Reply
catchwa said 6:25AM on 9-26-2007
Next time read the article, Ted. The have released a fix, it's called updating to the latest version.
Reply
Huw said 6:19PM on 9-26-2007
The second paragraph of that article says that not only is it version 2.0.4 *and prior*, but also that version 2.3 is unaffected.
I think you should post an apology, Ted.
Reply